[openstack-dev] [nova] Feature Freeze Exception for Add config drive support for PCS containers

2015-02-11 Thread aburluka
Hello, I'd like to request a feature freeze exception for the change [1] This change implements configuration drive support in Parallels containers. It does not change existing Nova behaviour. It's a last patch in parallels series, that implements blueprint pcs-support [2]. Previous patches of

Re: [openstack-dev] [nova] Feature Freeze Exception for Add config drive support for PCS containers

2015-02-16 Thread aburluka
release? Change is ready and does not have any objections except expired deadline note from Michael. Looking forward for your comments On 02/12/2015 04:26 PM, Daniel P. Berrange wrote: On Wed, Feb 11, 2015 at 03:28:49PM +0300, aburluka wrote: Hello, I'd like to request a feature freeze exception

Re: [openstack-dev] [nova] Feature Freeze Exception for Add config drive support for PCS containers

2015-02-16 Thread aburluka
Thank you so much for your help, Daniel On 02/16/2015 02:57 PM, Daniel P. Berrange wrote: On Mon, Feb 16, 2015 at 02:53:08PM +0300, aburluka wrote: Hi, There are some questions about FFE policy that are not obvious for me as a newbie. Last version of my change was submitted at February, 11th

[openstack-dev] [nova] Block Device Mapping is Invalid error

2015-03-16 Thread aburluka
Hello Nova! I'd like to ask community to help me with some unclear things. I'm currently working on adding persistent storage support into a parallels driver. I'm trying to start VM. nova boot test-vm --flavor m1.medium --image centos-vm-32 --nic net-id=c3f40e33-d535-4217-916b-1450b8cd3987

Re: [openstack-dev] [nova] Block Device Mapping is Invalid error

2015-03-17 Thread aburluka
--block-device id=1b6fd7a7-16b6-4053-91d1-41a625d6b185,source=image,device=sda,bootindex=0 Can you clarify please if API was changed since Juno release. Is it redundant since we specify --image param? On 03/16/2015 06:55 PM, aburluka wrote: Hello Nova! I'd like to ask community to help me