This message was deleted.
# _generals
Slackbot
05/19/2021, 6:22 PMThis message was deleted.
s
Scott Knights
05/20/2021, 1:41 AMDo you use MCSIO Ram cache? If changes have only been written to RAM and not flushed to disk then you will lose them at reboot. I haven't used MCS with AWS, so don't know if this is possible, but I have certainly seen this with MCSIO on VMWare.
r
rajneesh saraswat
05/20/2021, 1:53 AMYeah MCSIO is only with VMware not with AWS
j
James Kindon
05/20/2021, 8:13 AMYou should not be managing power management at the hypervisor (cloud) layer - this will upset CVAD - power management including scale should be driven via brokering commands (check out powerscale if you don’t have Citrix cloud)
j
James Rankin
05/20/2021, 8:16 AMWe use AWS workers, without MCS and using Terraform for the builds, but we still use AutoScale for power management and it works fine
j
James Kindon
05/20/2021, 9:51 AMYep - minute cvad has to deal with power management It should be the conductor
r
rajneesh saraswat
05/20/2021, 2:37 PMThis we have done to cope up the other thing also like we provide that test machine to install or upgrade app first instead of doing it on master image and if we allow poeerscale from citrix cloud it will wipe out the changes as design.
2 Views