Last active 4 weeks ago
Oh, I found how to have multiple profiles. That probably solves the problem for me. Wish me luck on trying to deploy this monstrosity....
Is it possible to have an image schema that is dynamic depending on the size of the hardware?
I have a reference Linux image that I built on a 20gb HDD VM, and I am modifying the slightly complex partitioning for deployment to larger hard drives.
Is it possible to do something like....
/boot - 1.5 gb static
/home - 35% of total hdd space, or 20gb, whichever is smaller
/var - 15% of total hdd space, or 10gb, whichever is smaller
/ - rest of the available space
If that's not possible, is it possible to have two deployment schemes for the same image? So I could create one for large hard drives with the smaller values, and one based on percentages?
Wanted to circle back and let you know how much I appreciate how quickly you responded.
This seems to have fixed it. Going to push forward and see if anything else breaks. I'll have to recapture this again in the not to distant future, any suggestion on how I could prevent it, or fix it on my own?
Here you go. In case it helps, here's how I did the partitioning.
CentOS7 Custom Partitioning.
I let the installer create the normal partitioning, and edited it to make partitions for the following...
boot, swap, var, var/log/audit, tmp, home, and root.
See attached, is this what you need? When I click the + under Volume Group, the server error occurs.
I uploaded a CentOS7 image with a custom partition scheme, and I want to adjust what happens with the partitions during deployment.
I open the image, go to Scheme, expand the LVM, and click the + to expand the Volume Group and there is a server error.
I am running 1.3.3
Any ideas? Thanks!
Server Error in '/clonedeploy' Application.
Object reference not set to an instance of an object.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
[NullReferenceException: Object reference not set to an instance of an object.]
CloneDeploy_ApiCalls.ImageSchemaAPI.GetLogicalVolumes(ImageSchemaRequestDTO schemaRequest) +167
CloneDeploy_Web.views.images.ImageSpecs.btnVG_Click(Object sender, EventArgs e) +471
System.Web.UI.WebControls.LinkButton.OnClick(EventArgs e) +133
System.Web.UI.WebControls.LinkButton.RaisePostBackEvent(String eventArgument) +147
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1664
I'm on 1.3.0
Looking at the upgrade now.... Thanks for quick reply.
Still having to run "dracut --force --regenerate-all" in a recovery kernel by the way, to get it to boot properly after deployment (for SOME systems).
I have some systems that are failing to expand the volume when doing a deploy. The reference system is built in a VM with a 10gb HDD, and it's being deployed to hardware with a 500gb Hard Drive. Once deployment is finished, the partitions are only 10gb.
Deploy log attached.
I am creating the image on VMWare Workstation 12 Pro. I've seen the issue happen on VMWare Workstation, VMWare vSphere, Hyper-V, and on physical hardware (but not always). The last deploy I tested came down on my VMWare Workstation with no errors - booted right up beautifully.
I realize this doesn't give you much to go on. Are there any logs from a client that failed to boot initially that might be valuable?