Re: juju2: how to edit a maas "cloud"?
Yes he can On Wed, Apr 27, 2016, 6:59 AM Andreas Hasenack wrote: > On Wed, Apr 27, 2016 at 1:04 PM, John Meinel > wrote: > >> >> >> On Wed, Apr 27, 2016 at 6:43 PM, Andreas Hasenack >> wrote: >> >>> On Wed, Apr 27, 2016 at 10:59 AM, John Meinel >>> wrote: >>> ... > >> As noted, the number of times you have to bootstrap should be going >> down, and if you are bootstrapping different-but-similar, then you again >> have a single config that can be reused. >> > > I'd love to be able to share a controller node with my colleagues. I > tried setting that up and creating a juju user, but in the end that user's > MAAS nodes were all allocated to "me" in MAAS, which was a bit unexpected. > The person running juju commands had his own MAAS credentials setup. Until > that is not setup, I can't keep a MAAS node allocated to my user 24/7, > it's > an expensive resource. I need to play with this shared controller idea a > bit more. > > > Were they using the same model or had they created their own model to work in? It may be that you had given them Admin rights on the controller, which meant that "juju add-model" then uses the admin credentials by default. I've heard that users that aren't admin but can create models are being prompted for what credentials should be used for this model. >>> >>> They were not admins. This is what I did, from memory: >>> - bootstrapped on MAAS >>> - created a model for user foo >>> - created user foo, with --share for that model >>> - granted user foo write access acl to model foo >>> - sent the register line to the user >>> >>> That user already had a cloud for this MAAS server, with credentials. He >>> ran the register command, then deployed services. The MAAS nodes that got >>> these services were under my name, not his. >>> >>> >> >> Unfortunately, for the 2.0 series the credentials used to manage machines >> are tied to the model. He'll need to create a different model (juju >> add-model --credentials XXX) to create machines with different credentials. >> The problem is that generally visibility between machines/security >> groups/etc is not guaranteed between >> > > Can he add another model without having to be an admin in the controller? > > > -- > Juju mailing list > Juju@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju > -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: juju2: how to edit a maas "cloud"?
On Wed, Apr 27, 2016 at 1:04 PM, John Meinel wrote: > > > On Wed, Apr 27, 2016 at 6:43 PM, Andreas Hasenack > wrote: > >> On Wed, Apr 27, 2016 at 10:59 AM, John Meinel >> wrote: >> >>> ... >>> >>> > As noted, the number of times you have to bootstrap should be going > down, and if you are bootstrapping different-but-similar, then you again > have a single config that can be reused. > I'd love to be able to share a controller node with my colleagues. I tried setting that up and creating a juju user, but in the end that user's MAAS nodes were all allocated to "me" in MAAS, which was a bit unexpected. The person running juju commands had his own MAAS credentials setup. Until that is not setup, I can't keep a MAAS node allocated to my user 24/7, it's an expensive resource. I need to play with this shared controller idea a bit more. >>> Were they using the same model or had they created their own model to >>> work in? It may be that you had given them Admin rights on the controller, >>> which meant that "juju add-model" then uses the admin credentials by >>> default. I've heard that users that aren't admin but can create models are >>> being prompted for what credentials should be used for this model. >>> >> >> They were not admins. This is what I did, from memory: >> - bootstrapped on MAAS >> - created a model for user foo >> - created user foo, with --share for that model >> - granted user foo write access acl to model foo >> - sent the register line to the user >> >> That user already had a cloud for this MAAS server, with credentials. He >> ran the register command, then deployed services. The MAAS nodes that got >> these services were under my name, not his. >> >> > > Unfortunately, for the 2.0 series the credentials used to manage machines > are tied to the model. He'll need to create a different model (juju > add-model --credentials XXX) to create machines with different credentials. > The problem is that generally visibility between machines/security > groups/etc is not guaranteed between > Can he add another model without having to be an admin in the controller? -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: juju2: how to edit a maas "cloud"?
On Wed, Apr 27, 2016 at 6:43 PM, Andreas Hasenack wrote: > On Wed, Apr 27, 2016 at 10:59 AM, John Meinel > wrote: > >> ... >> >> >>> As noted, the number of times you have to bootstrap should be going down, and if you are bootstrapping different-but-similar, then you again have a single config that can be reused. >>> >>> I'd love to be able to share a controller node with my colleagues. I >>> tried setting that up and creating a juju user, but in the end that user's >>> MAAS nodes were all allocated to "me" in MAAS, which was a bit unexpected. >>> The person running juju commands had his own MAAS credentials setup. Until >>> that is not setup, I can't keep a MAAS node allocated to my user 24/7, it's >>> an expensive resource. I need to play with this shared controller idea a >>> bit more. >>> >>> >>> >> Were they using the same model or had they created their own model to >> work in? It may be that you had given them Admin rights on the controller, >> which meant that "juju add-model" then uses the admin credentials by >> default. I've heard that users that aren't admin but can create models are >> being prompted for what credentials should be used for this model. >> > > They were not admins. This is what I did, from memory: > - bootstrapped on MAAS > - created a model for user foo > - created user foo, with --share for that model > - granted user foo write access acl to model foo > - sent the register line to the user > > That user already had a cloud for this MAAS server, with credentials. He > ran the register command, then deployed services. The MAAS nodes that got > these services were under my name, not his. > > Unfortunately, for the 2.0 series the credentials used to manage machines are tied to the model. He'll need to create a different model (juju add-model --credentials XXX) to create machines with different credentials. The problem is that generally visibility between machines/security groups/etc is not guaranteed between credentials on various providers. (Consider Virtual Private Cloud on AWS, different credentials may not even have the same network for machines to communicate to eachother.) It might be something that we can look into, but it requires a bunch of updates at the minimum (we'd need to start tracking individual credentials per machine, being able to handle split results when listing machines with each set of credentials, etc.) > >> So even if they are Admin, we do have: >> juju create-model --credential BLAH >> >> Which he can use to override the default credentials so that machines he >> provisions show up under his account. I do believe that this is a recent >> introduction in 2.0-beta. I do believe that we are currently modeling that >> all machines in a given model are provisioned with the same credentials. We >> may come back to this, but AIUI that is the plan for 2.0-final. >> >> > Cool. I'm on beta6 now, was on beta5 or earlier when I tried the above. > > Again, it is "model" level granularity, but you should be able to give him a space where he can manage his machines separately from yours, and have them show up that way in MaaS as well. John =:-> -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: juju2: how to edit a maas "cloud"?
On Wed, Apr 27, 2016 at 10:59 AM, John Meinel wrote: > ... > > >> >>> As noted, the number of times you have to bootstrap should be going >>> down, and if you are bootstrapping different-but-similar, then you again >>> have a single config that can be reused. >>> >> >> I'd love to be able to share a controller node with my colleagues. I >> tried setting that up and creating a juju user, but in the end that user's >> MAAS nodes were all allocated to "me" in MAAS, which was a bit unexpected. >> The person running juju commands had his own MAAS credentials setup. Until >> that is not setup, I can't keep a MAAS node allocated to my user 24/7, it's >> an expensive resource. I need to play with this shared controller idea a >> bit more. >> >> >> > Were they using the same model or had they created their own model to work > in? It may be that you had given them Admin rights on the controller, which > meant that "juju add-model" then uses the admin credentials by default. > I've heard that users that aren't admin but can create models are being > prompted for what credentials should be used for this model. > They were not admins. This is what I did, from memory: - bootstrapped on MAAS - created a model for user foo - created user foo, with --share for that model - granted user foo write access acl to model foo - sent the register line to the user That user already had a cloud for this MAAS server, with credentials. He ran the register command, then deployed services. The MAAS nodes that got these services were under my name, not his. > > So even if they are Admin, we do have: > juju create-model --credential BLAH > > Which he can use to override the default credentials so that machines he > provisions show up under his account. I do believe that this is a recent > introduction in 2.0-beta. I do believe that we are currently modeling that > all machines in a given model are provisioned with the same credentials. We > may come back to this, but AIUI that is the plan for 2.0-final. > > Cool. I'm on beta6 now, was on beta5 or earlier when I tried the above. -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: juju2: how to edit a maas "cloud"?
... > But where did the settings for scapestack get set up in the first place. >> You're missing some of the original "edit ~/.juju/environment.yaml" to >> insert the right information. >> >> > The scenario is starting from an already configured cloud in both juju1 > and juju2, and my use case is MAAS, not public clouds. Except in juju2 I > have to specify the configuration file everytime. If starting from scratch, > the juju2 way requires even more steps. > > >> If you are sharing information with someone else, being able to give them >> the file with all of the configuration becomes quite a bit easier, as you >> gave them the file, they saved it somewhere they know about, and then they >> pass that in to the bootstrap command. Rather than giving a snippet, that >> needs to be inserted into an existing file in the right place, and then it >> magically works if you named everything correctly. >> > > This configuration file you mention is far from complete. It's 1/3 of the > details, as it does not have, for example, the cloud endpoint, nor the > credentials. Just bootstrap-timeout, in my case. > > >> >> So while for people that have everything set up already, there is a bit >> more to write, for people coming to the system I think it is quite a bit >> more obvious for them. >> > > I think it's less obvious. At least it was less obvious to me, maybe > because of my juju1 experience. And changing is fine: just wanted to share > what my experience with this new process was. > > It's my understanding that there are 3 elements that you have to configure > in juju2, separately, when you start from scratch: cloud definition, > credential information and remaining configuration. In juju1 all 3 are in > the same environments.yaml section. All under the "environment" (now model) > name. > > You go from this one snippet (environments.yaml) to 3 files and 2 > commands. In juju2 you have to create a cloud file for MAAS, then create a > credentials file for that MAAS. Then import both (two commands), which > links the credentials to the "maas cloud". Then create a config file for > things that cannot be specified in the cloud definition file (like > bootstrap-timeout, crucial for the MAAS provider), and specify that > everytime you bootstrap. > So the cloud definition is something that needs to be created, but isn't that shareable? I'm actually wondering if it is something that we could get MaaS itself to generate, such that you go to a link on your running MaaS and it gives you the cloud definition file. It does look like we could do registration differently than a cloud definition file, though. For known cloud types, I think Juju knows most of the items (auth-types, etc at least would have sane defaults), and the only bit we'd really need is the auth-url. Something like: juju add-cloud mymaas --type maas --endpoint https://10.0.0.1/blah I guess one bit of complexity is that you can have multiple regions for a given cloud, so there is potentially a few endpoints. It does feel like streamlining the Maas case is something that would be worth spending a fair bit of time on. We do also have "juju add-credential cloud-name" that will start a "wizard" dialogue to prompt you for the user/password/auth-key bits that you need for the given cloud. I do think there was an interesting goal to separate the bits that are generic (everyone finds out about the same cloud endpoints, etc) from the things that are user specific (what is your username and password). From what is the particular details of this controller. One can certainly argue that bootstrap timeout is a property of the cloud itself (how long do machines take, on average, is not dependent on the individual controller, but a property of the overall cloud). > > >> As noted, the number of times you have to bootstrap should be going down, >> and if you are bootstrapping different-but-similar, then you again have a >> single config that can be reused. >> > > I'd love to be able to share a controller node with my colleagues. I tried > setting that up and creating a juju user, but in the end that user's MAAS > nodes were all allocated to "me" in MAAS, which was a bit unexpected. The > person running juju commands had his own MAAS credentials setup. Until that > is not setup, I can't keep a MAAS node allocated to my user 24/7, it's an > expensive resource. I need to play with this shared controller idea a bit > more. > > I wanted to split this bit into a different thread, because I do think there are aspects we want to make work well and polished here, separately from the "bootstrap" story. John =:-> -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: juju2: how to edit a maas "cloud"?
... > >> As noted, the number of times you have to bootstrap should be going down, >> and if you are bootstrapping different-but-similar, then you again have a >> single config that can be reused. >> > > I'd love to be able to share a controller node with my colleagues. I tried > setting that up and creating a juju user, but in the end that user's MAAS > nodes were all allocated to "me" in MAAS, which was a bit unexpected. The > person running juju commands had his own MAAS credentials setup. Until that > is not setup, I can't keep a MAAS node allocated to my user 24/7, it's an > expensive resource. I need to play with this shared controller idea a bit > more. > > > Were they using the same model or had they created their own model to work in? It may be that you had given them Admin rights on the controller, which meant that "juju add-model" then uses the admin credentials by default. I've heard that users that aren't admin but can create models are being prompted for what credentials should be used for this model. So even if they are Admin, we do have: juju create-model --credential BLAH Which he can use to override the default credentials so that machines he provisions show up under his account. I do believe that this is a recent introduction in 2.0-beta. I do believe that we are currently modeling that all machines in a given model are provisioned with the same credentials. We may come back to this, but AIUI that is the plan for 2.0-final. John =:-> -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: juju2: how to edit a maas "cloud"?
On Wed, Apr 27, 2016 at 9:55 AM, John Meinel wrote: > > > On Tue, Apr 26, 2016 at 10:41 PM, Andreas Hasenack > wrote: > >> On Tue, Apr 26, 2016 at 3:11 PM, John Meinel >> wrote: >> >>> I believe --config can take a file rather than just a 'key=value' >>> pairing. So you can save all your config to a file and pass it in with >>> '--config myconf.yaml' >>> >>> There was discussion of having a default search path for some of the >>> config, but I'm not sure if that got implemented, nor if it is actually >>> better since it is another magic place that you have to discover. >>> >>> >> This is the experience with juju 1: >> juju switch scapestack >> juju bootstrap >> >> This is the same experience with juju 2: >> juju bootstrap scapestack-controller scapestack --config >> ~/juju2-configs/scapestack.yaml >> >> > But where did the settings for scapestack get set up in the first place. > You're missing some of the original "edit ~/.juju/environment.yaml" to > insert the right information. > > The scenario is starting from an already configured cloud in both juju1 and juju2, and my use case is MAAS, not public clouds. Except in juju2 I have to specify the configuration file everytime. If starting from scratch, the juju2 way requires even more steps. > If you are sharing information with someone else, being able to give them > the file with all of the configuration becomes quite a bit easier, as you > gave them the file, they saved it somewhere they know about, and then they > pass that in to the bootstrap command. Rather than giving a snippet, that > needs to be inserted into an existing file in the right place, and then it > magically works if you named everything correctly. > This configuration file you mention is far from complete. It's 1/3 of the details, as it does not have, for example, the cloud endpoint, nor the credentials. Just bootstrap-timeout, in my case. > > So while for people that have everything set up already, there is a bit > more to write, for people coming to the system I think it is quite a bit > more obvious for them. > I think it's less obvious. At least it was less obvious to me, maybe because of my juju1 experience. And changing is fine: just wanted to share what my experience with this new process was. It's my understanding that there are 3 elements that you have to configure in juju2, separately, when you start from scratch: cloud definition, credential information and remaining configuration. In juju1 all 3 are in the same environments.yaml section. All under the "environment" (now model) name. You go from this one snippet (environments.yaml) to 3 files and 2 commands. In juju2 you have to create a cloud file for MAAS, then create a credentials file for that MAAS. Then import both (two commands), which links the credentials to the "maas cloud". Then create a config file for things that cannot be specified in the cloud definition file (like bootstrap-timeout, crucial for the MAAS provider), and specify that everytime you bootstrap. > As noted, the number of times you have to bootstrap should be going down, > and if you are bootstrapping different-but-similar, then you again have a > single config that can be reused. > I'd love to be able to share a controller node with my colleagues. I tried setting that up and creating a juju user, but in the end that user's MAAS nodes were all allocated to "me" in MAAS, which was a bit unexpected. The person running juju commands had his own MAAS credentials setup. Until that is not setup, I can't keep a MAAS node allocated to my user 24/7, it's an expensive resource. I need to play with this shared controller idea a bit more. -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: juju2: how to edit a maas "cloud"?
On Tue, Apr 26, 2016 at 10:41 PM, Andreas Hasenack wrote: > On Tue, Apr 26, 2016 at 3:11 PM, John Meinel > wrote: > >> I believe --config can take a file rather than just a 'key=value' >> pairing. So you can save all your config to a file and pass it in with >> '--config myconf.yaml' >> >> There was discussion of having a default search path for some of the >> config, but I'm not sure if that got implemented, nor if it is actually >> better since it is another magic place that you have to discover. >> >> > This is the experience with juju 1: > juju switch scapestack > juju bootstrap > > This is the same experience with juju 2: > juju bootstrap scapestack-controller scapestack --config > ~/juju2-configs/scapestack.yaml > > But where did the settings for scapestack get set up in the first place. You're missing some of the original "edit ~/.juju/environment.yaml" to insert the right information. If you are sharing information with someone else, being able to give them the file with all of the configuration becomes quite a bit easier, as you gave them the file, they saved it somewhere they know about, and then they pass that in to the bootstrap command. Rather than giving a snippet, that needs to be inserted into an existing file in the right place, and then it magically works if you named everything correctly. So while for people that have everything set up already, there is a bit more to write, for people coming to the system I think it is quite a bit more obvious for them. As noted, the number of times you have to bootstrap should be going down, and if you are bootstrapping different-but-similar, then you again have a single config that can be reused. John =:-> -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: juju2: how to edit a maas "cloud"?
Hi John -- thanks for the explanation. I wasn't suggesting another file the user would maintain, but instead a default set of configs I could attach to a cloud when I'm calling 'add-cloud'. It probably makes more sense in the case of MAAS where at least the bootstrap timeout often needs to be altered, as well as proxy settings (at a typical customer site). Thinking a bit further -- having a shared controller with users helps. But, in the case of MAAS, a PoC user (first time experience) would still struggle with it, I think. Especially dedicating a machine to a controller in their rack, and not seeing a way around it easily (abuse the admin model is the current answer). On Tue, Apr 26, 2016 at 12:11 PM, John Meinel wrote: > I believe --config can take a file rather than just a 'key=value' pairing. > So you can save all your config to a file and pass it in with '--config > myconf.yaml' > > There was discussion of having a default search path for some of the > config, but I'm not sure if that got implemented, nor if it is actually > better since it is another magic place that you have to discover. > > John > =:-> > > > On Tue, Apr 26, 2016 at 9:14 PM, David Britton < > david.brit...@canonical.com> wrote: > >> On Tue, Apr 26, 2016 at 11:58:38AM -0500, Cheryl Jennings wrote: >> > > >> > > On Apr 25, 2016 12:55, "Andreas Hasenack" >> wrote: >> > > >> > >> Uh, so in essence there are now three "files"? Cloud definition, >> config >> > >> for that cloud and credentials? And the config has to be passed each >> time, >> > >> whereas the other two are " imported"? >> > >> >> > > Yes, that's correct. 1 - The cloud definition (built in for public >> > clouds), 2 - credentials, and 3 - config that can be specified upon each >> > bootstrap. >> >> Are there any plans to allow this to be stored between controller >> bootstraps? >> >> Background -- We have some substrates where specifically the default >> timeout is too low for the maas provider. There are also considerations >> like proxies, apt proxies, etc that all become quite cumbersome to type >> and remember on the command line. >> >> -- >> David Britton >> >> -- >> Juju mailing list >> Juju@lists.ubuntu.com >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/juju >> > > -- David Britton -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: juju2: how to edit a maas "cloud"?
Yes, bootstrap is intended to be a rare task. Can any of the work done here be updated to create new models on a single bootstrap controller? Then the experience is even better with a single create-model call. On Tue, Apr 26, 2016, 8:42 AM Andreas Hasenack wrote: > On Tue, Apr 26, 2016 at 3:11 PM, John Meinel > wrote: > >> I believe --config can take a file rather than just a 'key=value' >> pairing. So you can save all your config to a file and pass it in with >> '--config myconf.yaml' >> >> There was discussion of having a default search path for some of the >> config, but I'm not sure if that got implemented, nor if it is actually >> better since it is another magic place that you have to discover. >> >> > This is the experience with juju 1: > juju switch scapestack > juju bootstrap > > This is the same experience with juju 2: > juju bootstrap scapestack-controller scapestack --config > ~/juju2-configs/scapestack.yaml > > > -- > Juju mailing list > Juju@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju > -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: juju2: how to edit a maas "cloud"?
On Tue, Apr 26, 2016 at 3:11 PM, John Meinel wrote: > I believe --config can take a file rather than just a 'key=value' pairing. > So you can save all your config to a file and pass it in with '--config > myconf.yaml' > > There was discussion of having a default search path for some of the > config, but I'm not sure if that got implemented, nor if it is actually > better since it is another magic place that you have to discover. > > This is the experience with juju 1: juju switch scapestack juju bootstrap This is the same experience with juju 2: juju bootstrap scapestack-controller scapestack --config ~/juju2-configs/scapestack.yaml -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: juju2: how to edit a maas "cloud"?
I believe --config can take a file rather than just a 'key=value' pairing. So you can save all your config to a file and pass it in with '--config myconf.yaml' There was discussion of having a default search path for some of the config, but I'm not sure if that got implemented, nor if it is actually better since it is another magic place that you have to discover. John =:-> On Tue, Apr 26, 2016 at 9:14 PM, David Britton wrote: > On Tue, Apr 26, 2016 at 11:58:38AM -0500, Cheryl Jennings wrote: > > > > > > On Apr 25, 2016 12:55, "Andreas Hasenack" > wrote: > > > > > >> Uh, so in essence there are now three "files"? Cloud definition, > config > > >> for that cloud and credentials? And the config has to be passed each > time, > > >> whereas the other two are " imported"? > > >> > > > Yes, that's correct. 1 - The cloud definition (built in for public > > clouds), 2 - credentials, and 3 - config that can be specified upon each > > bootstrap. > > Are there any plans to allow this to be stored between controller > bootstraps? > > Background -- We have some substrates where specifically the default > timeout is too low for the maas provider. There are also considerations > like proxies, apt proxies, etc that all become quite cumbersome to type > and remember on the command line. > > -- > David Britton > > -- > Juju mailing list > Juju@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju > -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: juju2: how to edit a maas "cloud"?
On Tue, Apr 26, 2016 at 11:58:38AM -0500, Cheryl Jennings wrote: > > > > On Apr 25, 2016 12:55, "Andreas Hasenack" wrote: > > > >> Uh, so in essence there are now three "files"? Cloud definition, config > >> for that cloud and credentials? And the config has to be passed each time, > >> whereas the other two are " imported"? > >> > > Yes, that's correct. 1 - The cloud definition (built in for public > clouds), 2 - credentials, and 3 - config that can be specified upon each > bootstrap. Are there any plans to allow this to be stored between controller bootstraps? Background -- We have some substrates where specifically the default timeout is too low for the maas provider. There are also considerations like proxies, apt proxies, etc that all become quite cumbersome to type and remember on the command line. -- David Britton -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: juju2: how to edit a maas "cloud"?
> > On Apr 25, 2016 12:55, "Andreas Hasenack" wrote: > >> Uh, so in essence there are now three "files"? Cloud definition, config >> for that cloud and credentials? And the config has to be passed each time, >> whereas the other two are " imported"? >> > Yes, that's correct. 1 - The cloud definition (built in for public clouds), 2 - credentials, and 3 - config that can be specified upon each bootstrap. -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: juju2: how to edit a maas "cloud"?
Forgot to include the list On Apr 25, 2016 12:55, "Andreas Hasenack" wrote: > Uh, so in essence there are now three "files"? Cloud definition, config > for that cloud and credentials? And the config has to be passed each time, > whereas the other two are " imported"? > On Apr 25, 2016 12:44, "Cheryl Jennings" > wrote: > >> Hi Andreas, >> >> The config is now separate from the cloud definition and can be passed in >> when bootstrapping using --config: >> >> juju bootstrap scapestack scapestack --config bootstrap-timeout=1800 >> >> You can also pass in a yaml file with config options if you don't want to >> type them all out on the command line: >> >> $ cat scapestack-config.yaml >> default-series: "trusty" >> logging-config: "=DEBUG" >> bootstrap-timeout: 1800 >> >> $ juju bootstrap scapestack scapestack --config=scapestack-config.yaml >> >> Thanks! >> -Cheryl >> >> On Mon, Apr 25, 2016 at 10:26 AM, Andreas Hasenack > > wrote: >> >>> On Mon, Apr 25, 2016 at 12:10 PM, Andreas Hasenack < >>> andr...@canonical.com> wrote: >>> Hi, I added a couple of maas servers to my cloud list: $ juju list-clouds CLOUD TYPEREGIONS aws ec2 us-east-1, us-west-1, us-west-2, eu-west-1, eu-central-1, ap-southeast-1, ap-southeast-2 ... ... local:beretstack maas local:scapestack maas I now want to add a bootstrap-timeout parameter to each. How do I do that? Do I need to recreate the yaml definition for each maas "cloud", add the parameter, and add-cloud --replace it? >>> >>> >>> That didn't work, btw: >>> >>> andreas@nsn7:~$ cat foo >>> clouds: >>> scapestack: >>> type: maas >>> auth-types: [oauth1] >>> endpoint: http://10.96.0.10/MAAS/ >>> bootstrap-timeout: 1800 >>> >>> andreas@nsn7:~$ juju add-cloud --replace scapestack foo >>> >>> andreas@nsn7:~$ juju show-cloud local:scapestack >>> defined: local >>> type: maas >>> auth-types: [oauth1] >>> endpoint: http://10.96.0.10/MAAS/ >>> >>> >>> >>> >>> >>> -- >>> Juju mailing list >>> Juju@lists.ubuntu.com >>> Modify settings or unsubscribe at: >>> https://lists.ubuntu.com/mailman/listinfo/juju >>> >>> >> -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: juju2: how to edit a maas "cloud"?
Hi Andreas, The config is now separate from the cloud definition and can be passed in when bootstrapping using --config: juju bootstrap scapestack scapestack --config bootstrap-timeout=1800 You can also pass in a yaml file with config options if you don't want to type them all out on the command line: $ cat scapestack-config.yaml default-series: "trusty" logging-config: "=DEBUG" bootstrap-timeout: 1800 $ juju bootstrap scapestack scapestack --config=scapestack-config.yaml Thanks! -Cheryl On Mon, Apr 25, 2016 at 10:26 AM, Andreas Hasenack wrote: > On Mon, Apr 25, 2016 at 12:10 PM, Andreas Hasenack > wrote: > >> Hi, >> >> I added a couple of maas servers to my cloud list: >> $ juju list-clouds >> CLOUD TYPEREGIONS >> aws ec2 us-east-1, us-west-1, us-west-2, eu-west-1, >> eu-central-1, ap-southeast-1, ap-southeast-2 ... >> ... >> local:beretstack maas >> local:scapestack maas >> >> I now want to add a bootstrap-timeout parameter to each. >> >> How do I do that? Do I need to recreate the yaml definition for each maas >> "cloud", add the parameter, and add-cloud --replace it? >> > > > That didn't work, btw: > > andreas@nsn7:~$ cat foo > clouds: > scapestack: > type: maas > auth-types: [oauth1] > endpoint: http://10.96.0.10/MAAS/ > bootstrap-timeout: 1800 > > andreas@nsn7:~$ juju add-cloud --replace scapestack foo > > andreas@nsn7:~$ juju show-cloud local:scapestack > defined: local > type: maas > auth-types: [oauth1] > endpoint: http://10.96.0.10/MAAS/ > > > > > > -- > Juju mailing list > Juju@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju > > -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: juju2: how to edit a maas "cloud"?
On Mon, Apr 25, 2016 at 12:10 PM, Andreas Hasenack wrote: > Hi, > > I added a couple of maas servers to my cloud list: > $ juju list-clouds > CLOUD TYPEREGIONS > aws ec2 us-east-1, us-west-1, us-west-2, eu-west-1, > eu-central-1, ap-southeast-1, ap-southeast-2 ... > ... > local:beretstack maas > local:scapestack maas > > I now want to add a bootstrap-timeout parameter to each. > > How do I do that? Do I need to recreate the yaml definition for each maas > "cloud", add the parameter, and add-cloud --replace it? > That didn't work, btw: andreas@nsn7:~$ cat foo clouds: scapestack: type: maas auth-types: [oauth1] endpoint: http://10.96.0.10/MAAS/ bootstrap-timeout: 1800 andreas@nsn7:~$ juju add-cloud --replace scapestack foo andreas@nsn7:~$ juju show-cloud local:scapestack defined: local type: maas auth-types: [oauth1] endpoint: http://10.96.0.10/MAAS/ -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
