You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by "Kelcey Damage (BBITS)" <ke...@bbits.ca> on 2012/10/18 23:18:59 UTC
cloud-setup-databases build 756
When running cloud-setup-databases, it auto chooses the highest priority nic(lowest number ie: eth0) for:
“Detected local IP address as 192.168.1.187, will use as cluster management server node IP[ OK ]”
Would it be possible to provide a new command line argument for establishing host? Such as: –host {ipaddr}
This would make complex deployment architectures easier to implement. It is also quite common to have multiple nics on the management server.
Is this feasible? Or too much work? Should I submit it as a bug?
http://www.backbone.gr/media/backbone_symbol1.pngKelcey Damage
Infrastructure Systems Architect
<http://www.backbonetechnology.com/> www.backbonetechnology.com
-------------------------------------------------------------------------
<ma...@bbits.ca> kelcey@bbits.ca
address: 55 East 7th Ave, Vancouver, BC, V5T 1M4
tel: +1 604 713 8560 ext:114
fax: +1 604 605 0964
skype: kelcey.damage
Re: cloud-setup-databases build 756
Posted by David Nalley <da...@gnsa.us>.
On Thu, Oct 18, 2012 at 5:18 PM, Kelcey Damage (BBITS) <ke...@bbits.ca> wrote:
>
> When running cloud-setup-databases, it auto chooses the highest priority nic(lowest number ie: eth0) for:
>
>
>
> “Detected local IP address as 192.168.1.187, will use as cluster management server node IP[ OK ]”
>
>
>
> Would it be possible to provide a new command line argument for establishing host? Such as: –host {ipaddr}
>
>
>
> This would make complex deployment architectures easier to implement. It is also quite common to have multiple nics on the management server.
>
>
>
> Is this feasible? Or too much work? Should I submit it as a bug?
>
>
Please submit as a bug.
--David
Re: cloud-setup-databases build 756
Posted by Rohit Yadav <ro...@citrix.com>.
On 23-Oct-2012, at 12:39 AM, Jessica Tomechak <je...@gmail.com> wrote:
>>
>> -----Original Message-----
>> From: Kelcey Damage (BBITS) [mailto:kelcey@bbits.ca]
>> Sent: Thursday, October 18, 2012 3:05 PM
>> To: cloudstack-dev@incubator.apache.org
>> Cc: Jessica Tomechak
>> Subject: RE: cloud-setup-databases build 756
>>
>> Looking at the latest build of 4.0.0 install guide, I find only the
>> following:
>>
>> 8. Set up the database. The following command creates the cloud user on
>> the database.
>> In dbpassword, specify the password to be assigned to the cloud user.
>> You can choose to provide no password.
>> In dbhost, provide the hostname of the database node.
>> In deploy-as, specify the username and password of the user deploying
>> the database. For example, if you originally installed MySQL with user
>> “root” and password “password”, provide --deploy-as=root:password.
>> (Optional) For encryption_type, use file or web to indicate the
>> technique used to pass in the database encryption password. Default: file.
>> See About Password and Key Encryption on page 34.
>> (Optional) For management_server_key, substitute the default key that is
>> used to encrypt confidential parameters in the CloudStack properties file.
>> Default: password. It is highly recommended that you replace this with a
>> more secure value. See About Password and Key Encryption on page 34.
>> (Optional) For database_key, substitute the default key that is used to
>> encrypt confidential parameters in the CloudStack database. Default:
>> password. It is highly recommended that you replace this with a more secure
>> value. See About Password and Key Encryption on page 34. #
>> cloud-setup-databases cloud:<dbpassword>@<dbhost>
>> --deploy-as=root:<password> -e <encryption_type> -m <management_server_key>
>> -k <database_key>
>>
>>
>> -----Original Message-----
>> From: Frank Zhang [mailto:Frank.Zhang@citrix.com]
>> Sent: Thursday, October 18, 2012 3:00 PM
>> To: cloudstack-dev@incubator.apache.org
>> Cc: Jessica Tomechak
>> Subject: RE: cloud-setup-databases build 756
>>
>>
>>> Subject: RE: cloud-setup-databases build 756
>>>
>>> That is true, but it does not seem to change once a zone is deployed.
>>> So if that 'undocumented' step is missed,
>>
>> Jessica, I think changing cluster.node.IP field should have documented in
>> chapters of setting up clustered mgmt servers. Am I right?
>>
>
>
> It's not documented there now. If such a procedure were added to the docs,
> that's where I would suggest adding it. Are you filing a doc bug to track
> the suggestion?
Filed the issue; https://issues.apache.org/jira/browse/CLOUDSTACK-404
>
> Jessica T.
> CloudStack Tech Pubs
>
>
>>
>>
>> the user needs to start redeploy the db
>>> with 'cloud-setup-databases cloud:password@127.0.0.1" (no deploy-as)
>>> and then reconfigure db.properties, and re-run "cloud-setup-management" .
>>>
>>> Kinda crazy and lengthy method. (Undocumented)
>>>
>>> -----Original Message-----
>>> From: Frank Zhang [mailto:Frank.Zhang@citrix.com]
>>> Sent: Thursday, October 18, 2012 2:35 PM
>>> To: CloudStack dev list
>>> Subject: RE: cloud-setup-databases build 756
>>>
>>> You can change the ip after running the script Go got
>>> /etc/cloud/management/db.properties, see cluster.node.IP field.
>>> Tough, having a CLI option would be a nice to have feature
>>>
>>> From: Kelcey Damage (BBITS) [mailto:kelcey@bbits.ca]
>>> Sent: Thursday, October 18, 2012 2:19 PM
>>> To: CloudStack dev list
>>> Subject: cloud-setup-databases build 756
>>>
>>> When running cloud-setup-databases, it auto chooses the highest
>>> priority nic(lowest number ie: eth0) for:
>>>
>>> “Detected local IP address as 192.168.1.187, will use as cluster
>>> management server node IP[ OK ]”
>>>
>>> Would it be possible to provide a new command line argument for
>>> establishing host? Such as: –host {ipaddr}
>>>
>>> This would make complex deployment architectures easier to implement.
>>> It is also quite common to have multiple nics on the management server.
>>>
>>> Is this feasible? Or too much work? Should I submit it as a bug?
>>>
>>> [cid:image001.png@01CDAD39.F8411B90]Kelcey Damage Infrastructure
>>> Systems Architect
>>> www.backbonetechnology.com<http://www.backbonetechnology.com/>
>>> ----------------------------------------------------------------------
>>> --- kelcey@bbits.ca<ma...@bbits.ca>
>>>
>>> address: 55 East 7th Ave, Vancouver, BC, V5T 1M4
>>> tel: +1 604 713 8560 ext:114
>>> fax: +1 604 605 0964
>>> skype: kelcey.damage
>>>
>>>
>>
>>
>>
Re: FW: cloud-setup-databases build 756
Posted by Jessica Tomechak <je...@gmail.com>.
>
> -----Original Message-----
> From: Kelcey Damage (BBITS) [mailto:kelcey@bbits.ca]
> Sent: Thursday, October 18, 2012 3:05 PM
> To: cloudstack-dev@incubator.apache.org
> Cc: Jessica Tomechak
> Subject: RE: cloud-setup-databases build 756
>
> Looking at the latest build of 4.0.0 install guide, I find only the
> following:
>
> 8. Set up the database. The following command creates the cloud user on
> the database.
> In dbpassword, specify the password to be assigned to the cloud user.
> You can choose to provide no password.
> In dbhost, provide the hostname of the database node.
> In deploy-as, specify the username and password of the user deploying
> the database. For example, if you originally installed MySQL with user
> “root” and password “password”, provide --deploy-as=root:password.
> (Optional) For encryption_type, use file or web to indicate the
> technique used to pass in the database encryption password. Default: file.
> See About Password and Key Encryption on page 34.
> (Optional) For management_server_key, substitute the default key that is
> used to encrypt confidential parameters in the CloudStack properties file.
> Default: password. It is highly recommended that you replace this with a
> more secure value. See About Password and Key Encryption on page 34.
> (Optional) For database_key, substitute the default key that is used to
> encrypt confidential parameters in the CloudStack database. Default:
> password. It is highly recommended that you replace this with a more secure
> value. See About Password and Key Encryption on page 34. #
> cloud-setup-databases cloud:<dbpassword>@<dbhost>
> --deploy-as=root:<password> -e <encryption_type> -m <management_server_key>
> -k <database_key>
>
>
> -----Original Message-----
> From: Frank Zhang [mailto:Frank.Zhang@citrix.com]
> Sent: Thursday, October 18, 2012 3:00 PM
> To: cloudstack-dev@incubator.apache.org
> Cc: Jessica Tomechak
> Subject: RE: cloud-setup-databases build 756
>
>
> > Subject: RE: cloud-setup-databases build 756
> >
> > That is true, but it does not seem to change once a zone is deployed.
> > So if that 'undocumented' step is missed,
>
> Jessica, I think changing cluster.node.IP field should have documented in
> chapters of setting up clustered mgmt servers. Am I right?
>
It's not documented there now. If such a procedure were added to the docs,
that's where I would suggest adding it. Are you filing a doc bug to track
the suggestion?
Jessica T.
CloudStack Tech Pubs
>
>
> the user needs to start redeploy the db
> > with 'cloud-setup-databases cloud:password@127.0.0.1" (no deploy-as)
> > and then reconfigure db.properties, and re-run "cloud-setup-management" .
> >
> > Kinda crazy and lengthy method. (Undocumented)
> >
> > -----Original Message-----
> > From: Frank Zhang [mailto:Frank.Zhang@citrix.com]
> > Sent: Thursday, October 18, 2012 2:35 PM
> > To: CloudStack dev list
> > Subject: RE: cloud-setup-databases build 756
> >
> > You can change the ip after running the script Go got
> > /etc/cloud/management/db.properties, see cluster.node.IP field.
> > Tough, having a CLI option would be a nice to have feature
> >
> > From: Kelcey Damage (BBITS) [mailto:kelcey@bbits.ca]
> > Sent: Thursday, October 18, 2012 2:19 PM
> > To: CloudStack dev list
> > Subject: cloud-setup-databases build 756
> >
> > When running cloud-setup-databases, it auto chooses the highest
> > priority nic(lowest number ie: eth0) for:
> >
> > “Detected local IP address as 192.168.1.187, will use as cluster
> > management server node IP[ OK ]”
> >
> > Would it be possible to provide a new command line argument for
> > establishing host? Such as: –host {ipaddr}
> >
> > This would make complex deployment architectures easier to implement.
> > It is also quite common to have multiple nics on the management server.
> >
> > Is this feasible? Or too much work? Should I submit it as a bug?
> >
> > [cid:image001.png@01CDAD39.F8411B90]Kelcey Damage Infrastructure
> > Systems Architect
> > www.backbonetechnology.com<http://www.backbonetechnology.com/>
> > ----------------------------------------------------------------------
> > --- kelcey@bbits.ca<ma...@bbits.ca>
> >
> > address: 55 East 7th Ave, Vancouver, BC, V5T 1M4
> > tel: +1 604 713 8560 ext:114
> > fax: +1 604 605 0964
> > skype: kelcey.damage
> >
> >
>
>
>
RE: cloud-setup-databases build 756
Posted by "Kelcey Damage (BBITS)" <ke...@bbits.ca>.
Looking at the latest build of 4.0.0 install guide, I find only the following:
8. Set up the database. The following command creates the cloud user on the database.
In dbpassword, specify the password to be assigned to the cloud user. You can choose to provide no password.
In dbhost, provide the hostname of the database node.
In deploy-as, specify the username and password of the user deploying the database. For example, if you originally installed MySQL with user “root” and password “password”, provide --deploy-as=root:password.
(Optional) For encryption_type, use file or web to indicate the technique used to pass in the database encryption password. Default: file. See About Password and Key Encryption on page 34.
(Optional) For management_server_key, substitute the default key that is used to encrypt confidential parameters in the CloudStack properties file. Default: password. It is highly recommended that you replace this with a more secure value. See About Password and Key Encryption on page 34.
(Optional) For database_key, substitute the default key that is used to encrypt confidential parameters in the CloudStack database. Default: password. It is highly recommended that you replace this with a more secure value. See About Password and Key Encryption on page 34. # cloud-setup-databases cloud:<dbpassword>@<dbhost> --deploy-as=root:<password> -e <encryption_type> -m <management_server_key> -k <database_key>
-----Original Message-----
From: Frank Zhang [mailto:Frank.Zhang@citrix.com]
Sent: Thursday, October 18, 2012 3:00 PM
To: cloudstack-dev@incubator.apache.org
Cc: Jessica Tomechak
Subject: RE: cloud-setup-databases build 756
> Subject: RE: cloud-setup-databases build 756
>
> That is true, but it does not seem to change once a zone is deployed.
> So if that 'undocumented' step is missed,
Jessica, I think changing cluster.node.IP field should have documented in chapters of setting up clustered mgmt servers. Am I right?
the user needs to start redeploy the db
> with 'cloud-setup-databases cloud:password@127.0.0.1" (no deploy-as)
> and then reconfigure db.properties, and re-run "cloud-setup-management" .
>
> Kinda crazy and lengthy method. (Undocumented)
>
> -----Original Message-----
> From: Frank Zhang [mailto:Frank.Zhang@citrix.com]
> Sent: Thursday, October 18, 2012 2:35 PM
> To: CloudStack dev list
> Subject: RE: cloud-setup-databases build 756
>
> You can change the ip after running the script Go got
> /etc/cloud/management/db.properties, see cluster.node.IP field.
> Tough, having a CLI option would be a nice to have feature
>
> From: Kelcey Damage (BBITS) [mailto:kelcey@bbits.ca]
> Sent: Thursday, October 18, 2012 2:19 PM
> To: CloudStack dev list
> Subject: cloud-setup-databases build 756
>
> When running cloud-setup-databases, it auto chooses the highest
> priority nic(lowest number ie: eth0) for:
>
> “Detected local IP address as 192.168.1.187, will use as cluster
> management server node IP[ OK ]”
>
> Would it be possible to provide a new command line argument for
> establishing host? Such as: –host {ipaddr}
>
> This would make complex deployment architectures easier to implement.
> It is also quite common to have multiple nics on the management server.
>
> Is this feasible? Or too much work? Should I submit it as a bug?
>
> [cid:image001.png@01CDAD39.F8411B90]Kelcey Damage Infrastructure
> Systems Architect
> www.backbonetechnology.com<http://www.backbonetechnology.com/>
> ----------------------------------------------------------------------
> --- kelcey@bbits.ca<ma...@bbits.ca>
>
> address: 55 East 7th Ave, Vancouver, BC, V5T 1M4
> tel: +1 604 713 8560 ext:114
> fax: +1 604 605 0964
> skype: kelcey.damage
>
>
RE: cloud-setup-databases build 756
Posted by Frank Zhang <Fr...@citrix.com>.
> Subject: RE: cloud-setup-databases build 756
>
> That is true, but it does not seem to change once a zone is deployed. So if
> that 'undocumented' step is missed,
Jessica, I think changing cluster.node.IP field should have documented in chapters of setting up clustered mgmt servers. Am I right?
the user needs to start redeploy the db
> with 'cloud-setup-databases cloud:password@127.0.0.1" (no deploy-as) and
> then reconfigure db.properties, and re-run "cloud-setup-management" .
>
> Kinda crazy and lengthy method. (Undocumented)
>
> -----Original Message-----
> From: Frank Zhang [mailto:Frank.Zhang@citrix.com]
> Sent: Thursday, October 18, 2012 2:35 PM
> To: CloudStack dev list
> Subject: RE: cloud-setup-databases build 756
>
> You can change the ip after running the script Go got
> /etc/cloud/management/db.properties, see cluster.node.IP field.
> Tough, having a CLI option would be a nice to have feature
>
> From: Kelcey Damage (BBITS) [mailto:kelcey@bbits.ca]
> Sent: Thursday, October 18, 2012 2:19 PM
> To: CloudStack dev list
> Subject: cloud-setup-databases build 756
>
> When running cloud-setup-databases, it auto chooses the highest priority
> nic(lowest number ie: eth0) for:
>
> “Detected local IP address as 192.168.1.187, will use as cluster management
> server node IP[ OK ]”
>
> Would it be possible to provide a new command line argument for
> establishing host? Such as: –host {ipaddr}
>
> This would make complex deployment architectures easier to implement. It
> is also quite common to have multiple nics on the management server.
>
> Is this feasible? Or too much work? Should I submit it as a bug?
>
> [cid:image001.png@01CDAD39.F8411B90]Kelcey Damage Infrastructure
> Systems Architect
> www.backbonetechnology.com<http://www.backbonetechnology.com/>
> -------------------------------------------------------------------------
> kelcey@bbits.ca<ma...@bbits.ca>
>
> address: 55 East 7th Ave, Vancouver, BC, V5T 1M4
> tel: +1 604 713 8560 ext:114
> fax: +1 604 605 0964
> skype: kelcey.damage
>
>
RE: cloud-setup-databases build 756
Posted by "Kelcey Damage (BBITS)" <ke...@bbits.ca>.
That is true, but it does not seem to change once a zone is deployed. So if that 'undocumented' step is missed, the user needs to start redeploy the db with 'cloud-setup-databases cloud:password@127.0.0.1" (no deploy-as) and then reconfigure db.properties, and re-run "cloud-setup-management" .
Kinda crazy and lengthy method. (Undocumented)
-----Original Message-----
From: Frank Zhang [mailto:Frank.Zhang@citrix.com]
Sent: Thursday, October 18, 2012 2:35 PM
To: CloudStack dev list
Subject: RE: cloud-setup-databases build 756
You can change the ip after running the script Go got /etc/cloud/management/db.properties, see cluster.node.IP field.
Tough, having a CLI option would be a nice to have feature
From: Kelcey Damage (BBITS) [mailto:kelcey@bbits.ca]
Sent: Thursday, October 18, 2012 2:19 PM
To: CloudStack dev list
Subject: cloud-setup-databases build 756
When running cloud-setup-databases, it auto chooses the highest priority nic(lowest number ie: eth0) for:
“Detected local IP address as 192.168.1.187, will use as cluster management server node IP[ OK ]”
Would it be possible to provide a new command line argument for establishing host? Such as: –host {ipaddr}
This would make complex deployment architectures easier to implement. It is also quite common to have multiple nics on the management server.
Is this feasible? Or too much work? Should I submit it as a bug?
[cid:image001.png@01CDAD39.F8411B90]Kelcey Damage Infrastructure Systems Architect www.backbonetechnology.com<http://www.backbonetechnology.com/>
-------------------------------------------------------------------------
kelcey@bbits.ca<ma...@bbits.ca>
address: 55 East 7th Ave, Vancouver, BC, V5T 1M4
tel: +1 604 713 8560 ext:114
fax: +1 604 605 0964
skype: kelcey.damage
RE: cloud-setup-databases build 756
Posted by Frank Zhang <Fr...@citrix.com>.
You can change the ip after running the script
Go got /etc/cloud/management/db.properties, see cluster.node.IP field.
Tough, having a CLI option would be a nice to have feature
From: Kelcey Damage (BBITS) [mailto:kelcey@bbits.ca]
Sent: Thursday, October 18, 2012 2:19 PM
To: CloudStack dev list
Subject: cloud-setup-databases build 756
When running cloud-setup-databases, it auto chooses the highest priority nic(lowest number ie: eth0) for:
“Detected local IP address as 192.168.1.187, will use as cluster management server node IP[ OK ]”
Would it be possible to provide a new command line argument for establishing host? Such as: –host {ipaddr}
This would make complex deployment architectures easier to implement. It is also quite common to have multiple nics on the management server.
Is this feasible? Or too much work? Should I submit it as a bug?
[cid:image001.png@01CDAD39.F8411B90]Kelcey Damage
Infrastructure Systems Architect
www.backbonetechnology.com<http://www.backbonetechnology.com/>
-------------------------------------------------------------------------
kelcey@bbits.ca<ma...@bbits.ca>
address: 55 East 7th Ave, Vancouver, BC, V5T 1M4
tel: +1 604 713 8560 ext:114
fax: +1 604 605 0964
skype: kelcey.damage
Re: cloud-setup-databases build 756
Posted by "Kelceydamage@bbits" <ke...@bbits.ca>.
Thanks Rohit, this is an awesome fix, and will help in the setup of complex installs.
Sent from my iPhone
On Oct 22, 2012, at 10:25 PM, Rohit Yadav <ro...@citrix.com> wrote:
> Hi kdamage, I did not see this thread, just saw the bug ticket and went ahead and fixed this in master:
> https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=commit;h=947d8cc6de6b69394457fd6f07d3bba82e14fd9f
>
> So, now you can do this:
> cloud-setup-database user:passwd@dbhost -i 192.168.1.10, or
> cloud-setup-database user:passwd@dbhost --mshost 192.168.1.10
>
> -i thinking ip, -h is already help; --host would be confusing (is it db host or ms host), hence --mshost.
>
> Please cherry pick if we want this in 4.0.
>
> For others on the thread;
> It was a simple fix, I went ahead and fixed it because the issue is how the code detects host IP, it always takes the lower nic and I think a user should be given power to explicitly set the host ip.
>
> Regards.
>
> On 19-Oct-2012, at 2:48 AM, Kelcey Damage (BBITS) <ke...@bbits.ca>> wrote:
>
> When running cloud-setup-databases, it auto chooses the highest priority nic(lowest number ie: eth0) for:
>
> “Detected local IP address as 192.168.1.187, will use as cluster management server node IP[ OK ]”
>
> Would it be possible to provide a new command line argument for establishing host? Such as: –host {ipaddr}
>
> This would make complex deployment architectures easier to implement. It is also quite common to have multiple nics on the management server.
>
> Is this feasible? Or too much work? Should I submit it as a bug?
>
> KELCEY DAMAGE
> Infrastructure Systems Architect
> www.backbonetechnology.com<http://www.backbonetechnology.com/>
> -------------------------------------------------------------------------
> kelcey@bbits.ca<ma...@bbits.ca>
>
> address: 55 East 7th Ave, Vancouver, BC, V5T 1M4
> tel: +1 604 713 8560 ext:114
> fax: +1 604 605 0964
> skype: kelcey.damage
>
>
Re: cloud-setup-databases build 756
Posted by Rohit Yadav <ro...@citrix.com>.
Hi kdamage, I did not see this thread, just saw the bug ticket and went ahead and fixed this in master:
https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=commit;h=947d8cc6de6b69394457fd6f07d3bba82e14fd9f
So, now you can do this:
cloud-setup-database user:passwd@dbhost -i 192.168.1.10, or
cloud-setup-database user:passwd@dbhost --mshost 192.168.1.10
-i thinking ip, -h is already help; --host would be confusing (is it db host or ms host), hence --mshost.
Please cherry pick if we want this in 4.0.
For others on the thread;
It was a simple fix, I went ahead and fixed it because the issue is how the code detects host IP, it always takes the lower nic and I think a user should be given power to explicitly set the host ip.
Regards.
On 19-Oct-2012, at 2:48 AM, Kelcey Damage (BBITS) <ke...@bbits.ca>> wrote:
When running cloud-setup-databases, it auto chooses the highest priority nic(lowest number ie: eth0) for:
“Detected local IP address as 192.168.1.187, will use as cluster management server node IP[ OK ]”
Would it be possible to provide a new command line argument for establishing host? Such as: –host {ipaddr}
This would make complex deployment architectures easier to implement. It is also quite common to have multiple nics on the management server.
Is this feasible? Or too much work? Should I submit it as a bug?
KELCEY DAMAGE
Infrastructure Systems Architect
www.backbonetechnology.com<http://www.backbonetechnology.com/>
-------------------------------------------------------------------------
kelcey@bbits.ca<ma...@bbits.ca>
address: 55 East 7th Ave, Vancouver, BC, V5T 1M4
tel: +1 604 713 8560 ext:114
fax: +1 604 605 0964
skype: kelcey.damage