Re: assignVirtualMachine - Change domain (4.1.1)

2014-09-09 Thread Ian Duffy 
Great! Thank you very much, thought I'd be out on my own for this.
On 10 Sep 2014 00:03, "John Kinsella"  wrote:

> Yeah - that doesn’t work 100% - you’ll have to delete and re-create the fw
> rules, at least for advanced networking. Needs a tiny bit more refinement.
> :)
>
> On Sep 9, 2014, at 3:42 PM, Nitin Mehta  nitin.me...@citrix.com>> wrote:
>
> Though I am averse to mucking around the db I know that John Kinsella
> spoke about it recently in the Bay Area meet up.
> Please find his slides (slide # 16) @
> http://www.slideshare.net/jlkinsel/dont-break-the-glass
>
> Thanks,
> -Nitin
>
> On 09/09/14 9:03 AM, "Ian Duffy"  wrote:
>
> Hi All,
>
> I'm wanting to use assignVirtualMachine to change the domain and account a
> VM belongs to within Cloudstack.
>
> Within version 4.1.1 this is not supported:
> http://cloudstack.apache.org/docs/api/apidocs-4.1/root_admin/assignVirtual
> Machine.html
>
> Transferring ownership to any domain was only implemented in a later
> release.
>
> Has anybody got a database modification work around for this?
>
> I'm looking at modifying the domain_id, domain_uuid, account_id,
> account_name, account_type for both volume and instance. I haven't tested
> this yet, but I would love to hear anybody elses experience.
>
> Thanks,
>
> Ian
>
>
> Stratosec - Secure Finance and Heathcare Clouds
> http://stratosec.co
> o: 415.315.9385
> @johnlkinsella
>
>

Re: assignVirtualMachine - Change domain (4.1.1)

2014-09-09 Thread John Kinsella 
Yeah - that doesn’t work 100% - you’ll have to delete and re-create the fw 
rules, at least for advanced networking. Needs a tiny bit more refinement. :)

On Sep 9, 2014, at 3:42 PM, Nitin Mehta 
mailto:nitin.me...@citrix.com>> wrote:

Though I am averse to mucking around the db I know that John Kinsella
spoke about it recently in the Bay Area meet up.
Please find his slides (slide # 16) @
http://www.slideshare.net/jlkinsel/dont-break-the-glass

Thanks,
-Nitin

On 09/09/14 9:03 AM, "Ian Duffy"  wrote:

Hi All,

I'm wanting to use assignVirtualMachine to change the domain and account a
VM belongs to within Cloudstack.

Within version 4.1.1 this is not supported:
http://cloudstack.apache.org/docs/api/apidocs-4.1/root_admin/assignVirtual
Machine.html

Transferring ownership to any domain was only implemented in a later
release.

Has anybody got a database modification work around for this?

I'm looking at modifying the domain_id, domain_uuid, account_id,
account_name, account_type for both volume and instance. I haven't tested
this yet, but I would love to hear anybody elses experience.

Thanks,

Ian


Stratosec - Secure Finance and Heathcare Clouds
http://stratosec.co
o: 415.315.9385
@johnlkinsella

Re: assignVirtualMachine - Change domain (4.1.1)

2014-09-09 Thread Nitin Mehta 
Though I am averse to mucking around the db I know that John Kinsella
spoke about it recently in the Bay Area meet up.
Please find his slides (slide # 16) @
http://www.slideshare.net/jlkinsel/dont-break-the-glass

Thanks,
-Nitin

On 09/09/14 9:03 AM, "Ian Duffy"  wrote:

>Hi All,
>
>I'm wanting to use assignVirtualMachine to change the domain and account a
>VM belongs to within Cloudstack.
>
>Within version 4.1.1 this is not supported:
>http://cloudstack.apache.org/docs/api/apidocs-4.1/root_admin/assignVirtual
>Machine.html
>
>Transferring ownership to any domain was only implemented in a later
>release.
>
>Has anybody got a database modification work around for this?
>
>I'm looking at modifying the domain_id, domain_uuid, account_id,
>account_name, account_type for both volume and instance. I haven't tested
>this yet, but I would love to hear anybody elses experience.
>
>Thanks,
>
>Ian

assignVirtualMachine - Change domain (4.1.1)

2014-09-09 Thread Ian Duffy 
Hi All,

I'm wanting to use assignVirtualMachine to change the domain and account a
VM belongs to within Cloudstack.

Within version 4.1.1 this is not supported:
http://cloudstack.apache.org/docs/api/apidocs-4.1/root_admin/assignVirtualMachine.html

Transferring ownership to any domain was only implemented in a later
release.

Has anybody got a database modification work around for this?

I'm looking at modifying the domain_id, domain_uuid, account_id,
account_name, account_type for both volume and instance. I haven't tested
this yet, but I would love to hear anybody elses experience.

Thanks,

Ian