Re: Specify lxd container bridge
Hey Corey, That specific error I haven't seen at that stage - allocating container addresses. Can you please paste the machine-0.log as well? Are you able to consistently reproduce this or it's intermittent? Cheers, Dimiter On 09/17/2016 12:17 AM, Corey Bryant wrote: > > > On Thu, Sep 1, 2016 at 4:25 AM, Dimiter Naydenov > mailto:dimiter.nayde...@canonical.com>> > wrote: > > Hello! > > When using juju 2.0 on maas 1.9 or 2.0, you should get lxd containers > provisioned with as many interfaces as their host machine has, because > we're creating bridges on all configured host interfaces at initial boot > (e.g. eth0 becomes br-eth0, ens4.250 - br-ens4.250 and so on). Nothing > needs configuring to get this behaviour, but there's a caveat: > > In order for the above to work, there's a limitation currently being > addressed - all interfaces on the host machine in MAAS need to be linked > to a subnet and have an IP address configured - either as Static or > Auto, but not DHCP or Unconfigured. Otherwise the process of allocating > addresses for the container (represented as a MAAS Device, visible on > the host node's details page in MAAS UI under Containers and VMs) can > fail half way through and Juju will instead fall back to a the single > NIC LXD default profile, using lxdbr0 on a local subnet. You can tell > whether this happened, because there will be a WARNING in > /var/log/juju/machine-0.log on the bootstrap machine, like: `failed to > prepare container "0/lxd/0" network config: ...` describing the > underlying error encountered. > > Please note, the above limitation will be gone very soon - likely > beta18, not beta17 scheduled for release this week. In that upcoming > beta, unlinked or unconfigured host machine interfaces won't prevent the > multi-NIC container provisioning and address allocation - Juju will just > allocate addresses where it can, leaving the rest unconfigured, and not > falling back to using LXD default profile's lxdbr0. > > HTH, > Dimiter > > > Hey Dimiter, > > I'm hitting the same issue. I have all the interfaces linked to subnets > with auto but I still get the 'failed to prepare container "0/lxd/0"' > error message saying 'connection is shut down'. The containers are > still using lxdbr0 (see http://paste.ubuntu.com/23188824/ > <http://paste.ubuntu.com/23188824/>). The containers show up on the > nodes page with juju*-lxd-*.maas names. Do you have any other tips for > getting past this? > > Thanks, > Corey -- Dimiter Naydenov Juju Core Sapphire team <http://juju.ubuntu.com> signature.asc Description: OpenPGP digital signature -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: Specify lxd container bridge
Hello! When using juju 2.0 on maas 1.9 or 2.0, you should get lxd containers provisioned with as many interfaces as their host machine has, because we're creating bridges on all configured host interfaces at initial boot (e.g. eth0 becomes br-eth0, ens4.250 - br-ens4.250 and so on). Nothing needs configuring to get this behaviour, but there's a caveat: In order for the above to work, there's a limitation currently being addressed - all interfaces on the host machine in MAAS need to be linked to a subnet and have an IP address configured - either as Static or Auto, but not DHCP or Unconfigured. Otherwise the process of allocating addresses for the container (represented as a MAAS Device, visible on the host node's details page in MAAS UI under Containers and VMs) can fail half way through and Juju will instead fall back to a the single NIC LXD default profile, using lxdbr0 on a local subnet. You can tell whether this happened, because there will be a WARNING in /var/log/juju/machine-0.log on the bootstrap machine, like: `failed to prepare container "0/lxd/0" network config: ...` describing the underlying error encountered. Please note, the above limitation will be gone very soon - likely beta18, not beta17 scheduled for release this week. In that upcoming beta, unlinked or unconfigured host machine interfaces won't prevent the multi-NIC container provisioning and address allocation - Juju will just allocate addresses where it can, leaving the rest unconfigured, and not falling back to using LXD default profile's lxdbr0. HTH, Dimiter On 08/31/2016 10:32 PM, Chance Ellis wrote: > Hello, > > > > I am running juju 2.0beta16 on trusty. I have a maas 2.0 rc4 cloud > bootstrapped. > > > > I am able to deploy services to lxd containers on xenial, but when I do > so, the container’s NIC is attached to lxdbr0 which seems to get some > arbitrary IP segment which in turn gives the container an IP from the > same segment. Is there a way I can instruct juju to specify the > bridge(s) I would like the container to use during deployment? > > > > Thanks! > Chance Ellis > > > > > > > -- Dimiter Naydenov Juju Core Sapphire team <http://juju.ubuntu.com> signature.asc Description: OpenPGP digital signature -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: openstack provider: hints about physical machines
On 05/13/2016 12:30 PM, Eddy Truyen wrote: > Hi, > > In openstack I often use the *--availability-zone nova: physical server>* option in the *nova boot* command to control the > placement of my openstack instances on physical machines of my openstack > cloud infrastructure > > Is it possible to specify this constraint as part of the *--constraint* > option in the *juju machine add command*? > > Best regards, > > Eddy > > Hey Eddy, Yes, you can use `juju add-machine zone=name` to place a machine within a zone. It's not a constraint, but a placement directive. See `juju help add-machine` for docs and examples. Cheers, -- Dimiter Naydenov Juju Core Sapphire team <http://juju.ubuntu.com> signature.asc Description: OpenPGP digital signature -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: compute-data network
On 05/04/2016 10:57 AM, Dimiter Naydenov wrote: > On 05/03/2016 10:07 PM, James Beedy wrote: >> Hello All, >> >> After reading Dimiter's >> post: >> https://insights.ubuntu.com/2015/11/08/deploying-openstack-on-maas-1-9-with-juju/, >> I have some questions regarding the network implementation. >> >> Can someone please link me to some docs describing the intrinsics of >> what a 'compute-data' network is? What services communicate on the >> 'compute-data' network? How is 'compute-data' network >> recognized/consumed by openstack charms and subsequent openstack services? >> >> Thanks! >> >> >> > Hey James, > > The compute-data network is used for guest VM traffic (instances started > by OpenStack) to other guest VMs or to OpenStack services. > If you have a look at the first post in the series, the architecture > diagram shows the different networks OpenStack uses (the ‘data’ network > there is called ‘compute-data’ in later posts, to distinguish it from > the ‘storage-data’ network). > > As for how the charms are configured to use those networks, I'm sure > some of the openstack charmers here can give you a more detailed answer. > > Cheers, > > > Sorry, I figured out you might be missing the link to that first article with the OpenStack diagram, so here it is: http://blog.naydenov.net/2015/11/deploying-openstack-on-maas-1-9-with-juju-network-setup/ -- Dimiter Naydenov Juju Core Sapphire team <http://juju.ubuntu.com> signature.asc Description: OpenPGP digital signature -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: compute-data network
On 05/03/2016 10:07 PM, James Beedy wrote: > Hello All, > > After reading Dimiter's > post: > https://insights.ubuntu.com/2015/11/08/deploying-openstack-on-maas-1-9-with-juju/, > I have some questions regarding the network implementation. > > Can someone please link me to some docs describing the intrinsics of > what a 'compute-data' network is? What services communicate on the > 'compute-data' network? How is 'compute-data' network > recognized/consumed by openstack charms and subsequent openstack services? > > Thanks! > > > Hey James, The compute-data network is used for guest VM traffic (instances started by OpenStack) to other guest VMs or to OpenStack services. If you have a look at the first post in the series, the architecture diagram shows the different networks OpenStack uses (the ‘data’ network there is called ‘compute-data’ in later posts, to distinguish it from the ‘storage-data’ network). As for how the charms are configured to use those networks, I'm sure some of the openstack charmers here can give you a more detailed answer. Cheers, -- Dimiter Naydenov Juju Core Sapphire team <http://juju.ubuntu.com> signature.asc Description: OpenPGP digital signature -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: EC2 VPC firewall rules
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 18.02.2016 12:01, Tom Barber wrote: > Hello folks > > I'm not sure if my tinkering has broken something, the fact I'm > running trunk has broken something or I just don't understand > something. > > Until last week we've been running EC2 classic, but we have now > switched to EC2-VPC and have launched a few machines. > > juju ssh to these machines works fine and I've been configuring > them to suit our needs. > > Then I came to look at external access, `juju expose mysqldb` for > example, I would then expect to be able to access it from the > outside world, but can't unless go into my VPC settings and open > the port in one of the juju security groups, at which point > external access works fine. > > Am I missing something? > > Thanks > > Tom > > Hey Tom, What you're describing sounds like a bug, as "juju expose " should trigger the firewaller worker to open the ports the service has declared (with open-ports within the charm) using the security group assigned to the host machine for all units of that service. Have you changed the "firewall-mode" setting by any chance? Can you provide some logs from /var/log/juju/*.log on the bootstrap instance (machine 0)? Cheers, - -- Dimiter Naydenov Juju Core Sapphire team <http://juju.ubuntu.com> -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJWxaAXAAoJENzxV2TbLzHwGgEIAIuj0sPzh7S/4jvTQ6aA/dwP i7WkSZ586JkNbEFeCBjDavO6oZFOwIAEW+EpGuy1C0O8BJr5Y2YJBMR96pdf3Rj/ Y6xS4Byt0HrwCWixt7ut6zu7BsT+nv6YFO7fNQvNYLyroufzpqUKaALJp5xwedkJ JIx1iyLnAZ4ZC1/0VkoBM/UjbZN7xQIteNvChBCZSSk8RvbqXCKhbXZKuUKMAw5g R+D3wIwLEyZHb5SATcSSdE6nidv4A0F2waac1/3lOvFebeOsnapnRKkIDp3Y9v19 /zDiDLWSJJvMDau8iIzSQ4STK/sLEmA78iRNkfDRWRifv0z1KkY6ppnhaS+jrj4= =kPA7 -END PGP SIGNATURE- -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: juju-br0 vs lxcbr0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 9.11.2015 04:23, Pshem Kowalczyk wrote: Hi Pshem, Any chance you've used JUJU_DEV_FEATURE_FLAGS=address-allocation during bootstrap? Can you have a look at /var/log/juju/machine-0.log? In the beginning there should be lines like: "address allocation feature disabled; using juju-br0 bridge for all containers" or alternatively: "address allocation feature enabled; using static IPs for containers: juju-br0" Cheers, Dimiter > Hi, > > I'm using MAAS and juju using lxc containers to spin up openstack > components. I regularly destroy my enviornments to try some new > settings. (juju 1.25, MAAS 1.8.2) > > Initially my setups would create a juju-br0 that contained eth0 and > then bridged all LXCs to it (this way I could use MAAS DHCP to give > IP addresses to containers). Somehow, between one test and the > other juju is not creating juju-br0 any more, and my LXC containers > end up living in lxcbr0 space with own DHCP server that gives them > 10.0.3.0/24 <http://10.0.3.0/24> IPs (which breaks connectivity > with anything outside of the machine) > > Clearly I must have changed something in my config, but my whole > definition of MAAS environment is quite simple: > > maas: type: maas maas-server: 'http://10.201.7.219/MAAS/' > maas-oauth: 'key here' bootstrap-timeout: 1800 lxc-default-mtu: > 9000 lxc-clone: true allow-lxc-loop-mounts: true > > and I don't recall modifying it. > > How can I get back to juju-br0 (that joins eth0 and assumes its IP > address)? > > kind regards Pshem > > > - -- Dimiter Naydenov Juju Core Sapphire team <http://juju.ubuntu.com> -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJWQEdiAAoJENzxV2TbLzHwdrcH/0WAQ0DVqK9PWVkHnpWsIUVQ kKGfpESiEpj/uR2OpZ5ijzKdIRBY/DRZyuvLEv2EUta4cx6irb8P9k0M66X3+7ub N3sXwK1m/b0I9H1u50dq269xwhUIS4Lu+pVdlIExZIbX8/9P0KxgARi3UXiBeAC7 5mawWFN7Pamxrnd0qZp6CGqExnC77q0vLLOqWXOewXkdBuIht6gEdq1+94e1ktVv 64rr7LI5sEY1j+v/HgeuZi8CPi44fNUTD3MEVtc6Ow2XSNU63b9xmrp40jE2iU55 islAdQU+VuUsyrcdp9hD1+6IiPcq/R82SIANumnPaNE7ONnRhHFOhhSxobZhYHo= =T2Fq -END PGP SIGNATURE- -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: Juju stable 1.25.0 is released
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 30.10.2015 01:06, Pshem Kowalczyk wrote:
>
> Hi
>
> On Fri, 30 Oct 2015 at 08:03 Curtis Hovey-Canonical
> mailto:cur...@canonical.com>> wrote:
>
> {cut}
>
> ### Support "devices" on MAAS 1.8+
>
> MAAS 1.8 introduced a new feature called "devices". This allows
> the association of a "device", that requires an IP address, with a
> parent machine managed by MAAS. There is a view in the MAAS UI
> showing all devices.
>
> With the "address-allocation" feature flag enabled, Juju will
> register LXC and KVM containers as devices on MAAS 1.8+. They are
> visible in the MAAS UI. If the environment is forcibly shut down,
> the IP addresses allocated to the containers will be released by
> MAAS.
>
> You can enable "address-allocation" is new Juju environments like
> so:
>
> JUJU_DEV_FEATURE_FLAG=address-allocation juju bootstrap
>
>
>
> Are they any other requirements in order to get the "devices"
> feature working? I've just built a brand new MAAS
> (1.8.2+bzr4041-0ubuntu1) and juju (1.25.0, from PPA) setup,
> bootstrapped a new environment using the syntax provided above, but
> the containers are not getting registered under 'MAAS devices'.
>
This is because recently MAAS web UI changed not to show devices as
before. However, juju should still be registering them for containers
and this can be verified by using the MAAS CLI:
$ maas devices list
Cheers,
Dimiter
> kind regards Pshem
>
>
>
- --
Dimiter Naydenov
Juju Core Sapphire team <http://juju.ubuntu.com>
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)
iQEcBAEBAgAGBQJWNx98AAoJENzxV2TbLzHwHaYIAKTrTftizH3fylyWSoOnbKJC
GcqofRaFd+g40bzvo2ZXMDHy3Tj2GhchrjKstP4pIfgDF3XnPKd6Q8g48+fyqXYJ
zIxmbrWr+RBjGdUPiW+uqaRB7E6i7EazOs4X0/XyJeMbx7TdrqD8d/0+i/Sv5Y/Y
EalgXIr8kciOhHw6IkNfBAMK6nxd2yAKxveWzPGD7z8wPBtDR5Y3PjmQHqevFf9Q
ofya8Z8TV0HFZHxb/ZAkkuLpxu9OXv69ReOux9Ai1MaGVEuEM2hMgv+MbC3RhlII
ZimTBotyzJckIi+IHL8UDOaOvsG6qAq9kA5FdUrlXhAfkPu66nEEK8bkTHVxuzk=
=foku
-END PGP SIGNATURE-
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
Re: LXC container and DNS names
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 29.10.2015 03:03, Pshem Kowalczyk wrote: > Hi, > > > I'm running a stable version of juju (1.24.7-trusty-amd64) and > maas (1.8.2+bzr4041-0ubuntu1 (trusty1)). I use maas to manage DHCP > and DNS on the 'bootstrap' network. > Yes, in fact registering containers in MAAS (along with their MACs, hostname, and parent instance) is what I'm working on currently. This will allow MAAS to release the resources allocated to containers (so far just IP addresses - static or DHCP-provided leases) when Juju destroys a container, its parent instance, or the whole environment (gracefully, i.e. without --force, or with --force, bypassing the usual shutdown Juju performs and relying on MAAS to do it instead). This will be the default behaviour starting from 1.24.8, and also will apply the upcoming 1.25.0 release, as well as all future releases. In order to be able to do that, for MAAS environments, Juju will require at least MAAS 1.8+. Containers will be registered as devices, and will have hostnames like "juju-machine-1-lxc-2.maas" (assuming regular instances get hostnames like "distinct-town.maas"). See bug https://bugs.launchpad.net/juju-core/+bug/1483879 for updates on when this feature will be available for early testing, or alternatively wait for the 1.24.8/1.25.0 releases. Regards, Dimiter > > I would like to know if it's possible to get juju to register the > DNS names for the containers it spins up. For example at this stage > I get: > > > > maascontroller:~$ juju status mysql > environment: maas machines: "0": agent-state: started > agent-version: 1.24.7 dns-name: controller.maas instance-id: > /MAAS/api/1.0/nodes/node-f2b1adb6-7603-11e5-a073-0050569a302e/ > series: trusty containers: 0/lxc/2: agent-state: started > agent-version: 1.24.7 dns-name: 10.0.0.148 instance-id: > juju-machine-0-lxc-2 series: trusty hardware: arch=amd64 hardware: > arch=amd64 cpu-cores=4 mem=65536M tags=4cpu > state-server-member-status: has-vote services: mysql: charm: > cs:trusty/mysql-29 exposed: false service-status: current: unknown > since: 29 Oct 2015 13:24:18+13:00 relations: cluster: - mysql > shared-db: - glance - keystone - neutron-api - neutron-gateway - > nova-cloud-controller - nova-compute units: mysql/0: > workload-status: current: unknown since: 29 Oct 2015 > 13:24:18+13:00 agent-status: current: idle since: 29 Oct 2015 > 13:34:53+13:00 version: 1.24.7 agent-state: started agent-version: > 1.24.7 machine: 0/lxc/2 public-address: 10.0.0.148 networks: > maas-eth1: provider-id: maas-eth1 cidr: 10.0.0.0/24 > <http://10.0.0.0/24> > > I would like juju to either create something like > juju-machine-0-lxc-2.maas (and preferably mysql-0.maas). Is this > possible? > > > kind regards > > Pshem > > > - -- Dimiter Naydenov Juju Core Sapphire team <http://juju.ubuntu.com> -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJWMhD1AAoJENzxV2TbLzHw4tgIAJKunUYnFq3GGQ3i5HbYT/mz AYD1RHpdL6vbph3egFJU7JJG1kIAapMz7ediOcU7XfGKlbIS4hjag3K042MQQyK/ TkFZOIzIVAhGIvvrGO5BpkSLQp6hOTjKKWPGppDsU9O7jUZo3rbHneVww3kNbTSl KDsLQHXZY1d1UCqX3OLsGQ/zUsgurcVQMjWVma+JygJkkNLJCKGkBdkQvqNJ/5jO 0T8gHJFpB3nrQfjQEt4Z2JJeX5OJLl0Zsil8vMxkPnVXjcNZQ7buPjsMght7eSOh OcnbNM8WOo2ANTdtw/FnjN0RNgzspTGRN1FLce+5LypvzOEjZbm4qC5DbsgJvRM= =b2W/ -END PGP SIGNATURE- -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: state of networking?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hey Kapil, Sorry for not responding earlier. You raised some good points re non-default VPC support. My plan was to introduce the support for specifying a VPC ID to use, while also making sure initially Juju keeps the same behaviour and experience as if the VPC was a default VPC (hence the validation I mentioned). Once we have support for passing VPCID across the board in the EC2 provider, we can relax those requirements we're expecting the specified VPC to meet (e.g. just print / log a warning instead of refusing to use it). We do fully intend to support a VPC without public IPs etc. later this year, but first we need to solve the issue with API server nodes accessibility for all nodes in the environment (this requirement won't change as Juju agents need to be able to connect to the API server(s) regardless). As for the new features in coming up in 1.25, more documentation will be added in time for the release on how to use spaces etc. We're actively soliciting feedback on spaces support and their implementation. Only EC2 is supported for now and there are a few rough edges still (e.g. it's not *yet* working end-to-end, but it will be after I land a few fixes today in 1.25 and master). Cheers, Dimiter On 17.09.2015 15:09, Kapil Thangavelu wrote: > The network support listed in the 1.25 alpha release notes ( > https://lists.ubuntu.com/archives/juju-dev/2015-August/004721.html > ) looks pretty good, i'll give it a whirl. > > > On Tue, Sep 15, 2015 at 7:11 AM, Kapil Thangavelu > mailto:kap...@gmail.com>> wrote: > > Its been hard to see much progress on this and i wanted to checkin > wrt to the current state. > > The requirement of public ip on for the subnets sort of defeats > the purpose of supporting non default vpcs. The use of vpc is > typically around network segmentation and isolation semantics, ie > db and app tier subnets don't have public ips by design. In fact at > larger orgs, its not typical that an app deployment team would even > have access to rearrange the network topology on demand. The > learned model of inform juju of the network topology for a given > env by defining/importing netspace/zone from extant subnets is more > typical. > > cheers, kapil > > > On Fri, Jul 24, 2015 at 3:44 PM, Dimiter Naydenov > <mailto:dimiter.nayde...@canonical.com>> wrote: > > On 23.07.2015 22:57, Kapil Thangavelu wrote: >> I've talked to a few folk at some conferences, but i'm curious >> what's been happening in networking? > >> it feels like its been fairly long time w/ little visible >> progress on end user features. particularly i'm curious about aws >> (ie. the worlds biggest cloud :-).. more concretely - can i use >> existing (non default) vpcs? - can i create/use extant subnets >> across zones and specify them for services? - can i control >> routing between subnets or alternatively control/enforce iptables >> for a service based on extant relations (optional)? > >> afaics most of the network progress was in various client libs >> afaics over the last year (and a maas centric core network >> model)... are there any plans to switch out to the aws api sdk >> instead of maintaining a separate client lib? > >> thanks, > >> Kapil > > > > Hey Kapil, > > I can report some progress on the points you've asked about: 1) > non-default VPC support is mostly done - see bug > https://bugs.launchpad.net/juju-core/+bug/1321442, which I have > mostly finished fixing. In brief, there will be a "vpc-id" environ > setting that can be used to specify a non-default (but compatible) > VPC to use. By compatible at this stage I mean 2 things: at least > one subnet per AZ, all subnets in the VPC have MapPublicIPOnLaunch > set. 2) the AWS VPC support is ongoing in a feature branch, the > MVP proposal will include: add existing subnet to juju (make juju > aware of it); create a space including one or more subnets; deploy > a service within a space. 3) it's on the roadmap to do more > sophisticated routing/ACL/firewalling between spaces, but it won't > happen until the 16.04 time frame most likely. > > HTH, Dimiter > > -- Juju mailing list Juju@lists.ubuntu.com > <mailto:Juju@lists.ubuntu.com> Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju > > > - -- Dimiter Naydenov Juju Core Sapphire team <http://juju.ubuntu.com> -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJV+rgZAAoJENzxV2TbLzHw1mQIALgBwnhhcYoTgwyCU9shUpy2 I+YkbIeJ4wcpaEGAHjIWkKNYPfRiCK8MOyx+X9r0xI2enyztRBvoYwABLOwkMnP4 UyGXcNewD3S4hvgJJMSe9YgI8Xup3AO4M5eCFx
Re: bootstrap constraints
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 27.08.2015 07:29, Matt Rae wrote: > Hi All, when using 'juju bootstrap --constraints' the constraint is > used for bootstrap, but the constraint is also set on the > environment for future machines. > > Is it helpful to set the additional environment constraint? > > So far I've frequently seen the bootstrap constraint used to > choose which node to bootstrap to, for example 'juju bootstrap > --constraints "tags=juju"'. In this case, normally the constraint > set on the environment needs to be cleared after bootstrap to > deploy to machines not tagged 'juju'. > > With bootstrap --constraints at least we can clear the constraint > after bootstrap completes, but with quickstart --constraints, there > doesn't appear to be way to clear the constraint before juju gui > starts deploying the bundle using the environment constraint which > I don't want to use for additional machines. So it appears to break > the use case of using --constraints to bootstrap to a particular > machine. > > Matt > > Hi Matt, When you're saying you're unable to clear the constraints set at bootstrap from the environment, do you mean "tags" specifically, or other constraints as well? If the former, but not the latter, read on. I've recently discovered there's *no* way to unset a bootstrap (or environment) constraint value of type list (e.g. "tags=aa,bb,^cc,dd", mostly undocumented "networks=..." and since a few days - "spaces=..." with the same format). This issue appears to have been lurking for a long time - just try this: $ juju environment set-constraints tags=foo,^bar $ juju environment get-constraints tags=foo,^bar $ juju environment set-constraints tags= # expected: set to empty $ juju environment get-constraints tags=foo,^bar So, I fixed this on master a few days ago, and in 1.25 it *will* be possible to unset list-style constraints (note that, as before, you can still set them to different non-empty value). If your issue is like described above, you might want to give 1.25-alpha1 a try. Cheers, - -- Dimiter Naydenov Juju Core Sapphire team <http://juju.ubuntu.com> -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJV3qx5AAoJENzxV2TbLzHwTlMIAJMdw42RU3BY8kvb1Yk4G+6h gGn0XEDPyJHmzgB/QLBjcrjW4FBXFGmJuN/vmbO/0uW6niZINBkHwTDT2m82aNan uOIBjaMQxM6GQiLcYXqWroWb1V2dKxgfMx9e+5F5ggmmy6fCtcSrGR4TzAfC62VL +GXwvv1sLCLudyjBFhAycu6JMLcONrmw9ZWdN0ZAuPwMYGPWqqY/E3WM4Z7FTWv1 r9Igt14ogoYwG4kzx2K3xzbLkZP4gfr7pJDGSSjaDUh12Y7jXMYklqLKPFrojcEU NPU+vLun0jPKVZOwC5QNYDBqFP+eppOdqNPeT+HKjkfgv5RP6C3sK7FXt14HmQI= =7Hyn -END PGP SIGNATURE- -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: Fwd: How to do network segregation with Juju deployment ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Specifying juju deploy with --networks does bring nodes on MAAS, but that won't work for deploying directly inside a container (as this is done by Juju and the support for that is not completed yet). You could try: juju deploy .. --networks net_public,net_internal,^net_dmz (without --to though). The argument of --networks has the same format as for --constraints tags=.. (comma-delimited, allowing to use ^ as prefix for excluding networks) and the list entries must match network names in MAAS. Alternatively, you can tag your nodes according to the networks they are on, and then use juju deploy with --constraints tags=.. as suggested below (without --to though, as above). You don't need juju machine add... first and so then deploy --to it, unless you want to deploy in containers. Deploying like this but on containers (and setting up multiple NICs on them connected to their host NICs) is under development and not yet supported. So unfortunately manual steps will be needed to configure the NICs on the containers. If done inside the lxc-template container juju creates (with lxc-clone: true) it could be somewhat automated. Cheers, Dimiter On 7.08.2015 21:22, Daniel Bidwell wrote: > Does the --networks=... actually bring up the maas nodes? > > That would be simpler then doing "juju machine add ..." going in > and bringing up the interfaces and then doing "juju deploy > --to n". > > On Fri, 2015-08-07 at 18:52 +0300, Dimiter Naydenov wrote: >> Hi, >> >> We're in currently developing more comprehensive networking >> features in Juju, so soon you'll be able to configure this with >> Juju the way you like it. >> >> In the meantime, please ignore the --networks argument - it was >> implemented partially as a proof of concept and never officially >> supported or documented (it's only supported on MAAS and only >> for nodes, not LXC containers or KVM instances). >> >> If you want to get a node from MAAS on given networks, I'd >> suggest to add tags on the nodes (e.g. tag "net_public", >> "net_internal") and then use --constraints instead: $ juju deploy >> keystone --constraints tags=net_internal,^net_public >> >> Multiple tags can be specified in a comma-delimited list. If you >> prefix a tag with "^" it means "not this tag" (i.e. exclude >> nodes matching that tag before deciding which node to >> provision). >> >> I hope this helps, and stay tuned for the upcoming networking >> features in Juju! >> >> Cheers, Dimiter Naydenov >> >> On 7.08.2015 18:16, 曾建銘 wrote: >>> Hi all, >>> >>> I want to deploy OpenStack by Juju with network segregation. I >>> got 3 different subnets in my environment, and follow bellow >>> steps to config: >>> >>> 1. Set interfaces information in MAAS clusters tab. 2. Set >>> networks information in MAAS networks tab. 3. Edit the network >>> detail and set connected interface cards. >>> >>> I got two screen shots to display my current settings. >>> >>> >>> >>> >>> Then, I used below commands try to deploy keystone service in >>> LXC with multiple networks: $ juju bootstrap $ juju deploy >>> keystone --networks=net_public,net_admin,net_internal >>> --config=config.yaml --to lxc:0 >>> >>> But it stuck for a long time with allocating status, so I >>> checked the juju debug logs, then I found logs as below: >>> "ERROR juju.provisioner provisioner_task.go:630 cannot start >>> instance for machine "0/lxc/1": starting lxc containers with >>> networks is not supported yet" >>> >>> Is there anything I missed? Why juju told me "networks is not >>> supported yet"? >>> >>> I have stuck with this problem for several days. If anyone >>> have one minute to give me some hints, I will be very >>> appreciate. >>> >>> Best Regards, Leon >>> >>> >>> >> >> > - -- Dimiter Naydenov Juju Core Sapphire team <http://juju.ubuntu.com> -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJVxj5lAAoJENzxV2TbLzHwko4H/ipvJCotsIvgjy1M3DXQOpu6 FKvgSwzJLGvkLwGt+upA6Lj055SCxnvhcUd2yaIOwPGJ5etQknOLv7ONNVS2q5P5 Td7TgJXE7N0/pjQ1aGRVARVEeu3JSrHAXoQQ9ihi1BF74yINXqQ3H2IDkot84oNe G8JHLlsfSAxY+8iyd2YpCbe1C3QH4RhdV/8rj/XZuhsB0qzkHjUflZjAOLor/vzu EAD92FRjrOyewK/ON7yH0Z21VXbmWGV9Rfl815MCqXWdXaD9ZZCpscnuoqFajcTy +10PEg1NiPgY3/vcabKR1ceRHnhkqDilJ+0qhyXAUpvtQULNQfOe11UQPr4IH1k= =rJBS -END PGP SIGNATURE- -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: Fwd: How to do network segregation with Juju deployment ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, We're in currently developing more comprehensive networking features in Juju, so soon you'll be able to configure this with Juju the way you like it. In the meantime, please ignore the --networks argument - it was implemented partially as a proof of concept and never officially supported or documented (it's only supported on MAAS and only for nodes, not LXC containers or KVM instances). If you want to get a node from MAAS on given networks, I'd suggest to add tags on the nodes (e.g. tag "net_public", "net_internal") and then use --constraints instead: $ juju deploy keystone --constraints tags=net_internal,^net_public Multiple tags can be specified in a comma-delimited list. If you prefix a tag with "^" it means "not this tag" (i.e. exclude nodes matching that tag before deciding which node to provision). I hope this helps, and stay tuned for the upcoming networking features in Juju! Cheers, Dimiter Naydenov On 7.08.2015 18:16, 曾建銘 wrote: > Hi all, > > I want to deploy OpenStack by Juju with network segregation. I got > 3 different subnets in my environment, and follow bellow steps to > config: > > 1. Set interfaces information in MAAS clusters tab. 2. Set networks > information in MAAS networks tab. 3. Edit the network detail and > set connected interface cards. > > I got two screen shots to display my current settings. > > > > > Then, I used below commands try to deploy keystone service in LXC > with multiple networks: $ juju bootstrap $ juju deploy keystone > --networks=net_public,net_admin,net_internal --config=config.yaml > --to lxc:0 > > But it stuck for a long time with allocating status, so I checked > the juju debug logs, then I found logs as below: "ERROR > juju.provisioner provisioner_task.go:630 cannot start instance for > machine "0/lxc/1": starting lxc containers with networks is not > supported yet" > > Is there anything I missed? Why juju told me "networks is not > supported yet"? > > I have stuck with this problem for several days. If anyone have > one minute to give me some hints, I will be very appreciate. > > Best Regards, Leon > > > - -- Dimiter Naydenov Juju Core Sapphire team <http://juju.ubuntu.com> -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJVxNROAAoJENzxV2TbLzHw+qIIAJqX9LGyhzLT9geKxSJQaEcW oqtf5WGcgDECf5K/lFgqRtoQRm8m/BYvZx+kw2u4bzwlCtdf7XplO3Di53DDVMib sc/ox2S+zhqwMXav3CrCy0P66uVNh9zCgjeo+Wbs3V5KCCLf/FHNUfLdi3XCpF4x ZDyWVuBtICO0j/3OPglwE4iBSy0jUE7ZYaB0O2i4LgL6ednLgB4DOLmehjC6B2IO AUX7GPHdYCodsc92mySfjMasGTi7gomPGSggOhy/iF7GO3Anx12aCSIdZuVGXpNx Woltz3Id6TR8ZVnbdPQD4YpFF+l2iLw/YKTO6it1+izRBnEpksxJvThjoo05//o= =ifY7 -END PGP SIGNATURE- -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: state of networking?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 23.07.2015 22:57, Kapil Thangavelu wrote: > I've talked to a few folk at some conferences, but i'm curious > what's been happening in networking? > > it feels like its been fairly long time w/ little visible progress > on end user features. particularly i'm curious about aws (ie. the > worlds biggest cloud :-).. more concretely - can i use existing > (non default) vpcs? - can i create/use extant subnets across zones > and specify them for services? - can i control routing between > subnets or alternatively control/enforce iptables for a service > based on extant relations (optional)? > > afaics most of the network progress was in various client libs > afaics over the last year (and a maas centric core network > model)... are there any plans to switch out to the aws api sdk > instead of maintaining a separate client lib? > > thanks, > > Kapil > > > Hey Kapil, I can report some progress on the points you've asked about: 1) non-default VPC support is mostly done - see bug https://bugs.launchpad.net/juju-core/+bug/1321442, which I have mostly finished fixing. In brief, there will be a "vpc-id" environ setting that can be used to specify a non-default (but compatible) VPC to use. By compatible at this stage I mean 2 things: at least one subnet per AZ, all subnets in the VPC have MapPublicIPOnLaunch set. 2) the AWS VPC support is ongoing in a feature branch, the MVP proposal will include: add existing subnet to juju (make juju aware of it); create a space including one or more subnets; deploy a service within a space. 3) it's on the roadmap to do more sophisticated routing/ACL/firewalling between spaces, but it won't happen until the 16.04 time frame most likely. HTH, Dimiter - -- Dimiter Naydenov Juju Core Sapphire team <http://juju.ubuntu.com> -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJVspWBAAoJENzxV2TbLzHwoxkH/RM5JcXSNtL3wyLxafGbaCos XMNEQAnMSE/EtQerDEfuu2GFA+Un1Rc0ng6gN6322uc0Ey3OSY9IQ2s8fGhaKFJh NiBVHgLtlC77lKoIMGDyGf6OXXTRqZC/T/kM2Z2xrdWNcyVMySi2jH1+2kab+Ljr 3hwKc546DjVpaigqLx/Tq66G2yoyrS8ITdudgK8K6LmPf7hUWLMPCbYam/Dw+yuC PSiD2J8VNklOsg8U7zDPAyMcL+3ymyyIbp6aZRn5o6Hmkgfo64P+9J6waqFCfGTz qtEE3PTHneajXES9ewOiTbY0NKn7joT2T5qlxJjrMVXeIYqzGId0iaIVwIgi1DI= =p2Df -END PGP SIGNATURE- -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: Specify Amazon VPC/Subnet
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Mark, I'm not sure you've got my earlier reply to your question, please have a look at bug https://bugs.launchpad.net/juju-core/+bug/1321442 which I've started working on. My proposal is to allow specifying a "vpc-id" config setting - if set, it will be used if possible instead of the default VPC. Cheers, Dimiter On 14.07.2015 23:22, Mark Hannessen wrote: > Anyone any idea if deploying inside an existing EC2 VPC/Subnet is > possible? > > I found someone who proposed a patch for this a long time ago but > haven't been able to find anything like this for a more recent > version. > > https://bugs.launchpad.net/juju/+bug/1073133 > > Met vriendelijke groet, > > Mark Hannessen > > > Senior System Administrator / Architect Tel: +31 50 5775822-9702 > Mob: 06 414 10 181 E-mail: m.hannes...@youwe.nl > > - Oorspronkelijk bericht - Van: "Mark Hannessen" > Aan: "juju" > Verzonden: Maandag 13 juli 2015 10:21:03 Onderwerp: Specify Amazon > VPC/Subnet > > Hi, > > For one of our customers we seek to deploy a juju setup inside of a > Amazon VPC. I have already configured the VPC with an internal > gateway and am able to boot machines inside of it as expected. > Internet connectivity works as expected. > > Unfortunately juju bootstrap does not seem to deploy the bootstrap > node inside the VPC by default. juju bootstrap --constraints > "cpu-cores=1" --upload-series trusty --upload-tools --to > zone=eu-west-1a > > I suspect i need a parameter to specify the subnet of the VPC > (subnet-06932f5f) but i couldn't find it on > https://jujucharms.com/docs/devel/config-general > > You can see my current configuration below. > > default: amazon > > environments: amazon: type: "ec2" region: "eu-west-1" access-key: > "" secret-key: "" image-stream: "released" > default-series: trusty > > > Anyone any idea as to how to make this work? > > Kind Regards, > > Mark > - -- Dimiter Naydenov Juju Core Sapphire team <http://juju.ubuntu.com> -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJVphXvAAoJENzxV2TbLzHwDSwH/1+4LVPvMYAJ0CHbvE7evJT7 7k55TxWwL9rLTnxPhHYl41wJQeM3K361Bycw+5ADxq/Og+gOANrNys/a7TNj4jcO apn5GUMV7Ss74y8kT/y70wiTCDte71CFVxsTcxdf9XP+8FwjVhuAfXcq+SBBWf6e IGQNyqPaGipt8EnVe/7WOmWRdqDEcj4YHYFKiG4UFBoJu45gj1QCXcWOgqzGVe85 9fZ83xuSGlk2I3RF5hug5M0cxmQdvc10Oh0PpM3yt1Kagf4wk1ww1HfC45qod+Ra 61RlVDaIzdLDBOfmRmlX41Tr933AxvotCJRcKbMq0U0KTKcYMSFCkOlCN7M73BE= =Sm2G -END PGP SIGNATURE- -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: Specify Amazon VPC/Subnet
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Mark, It seems you're hitting a known bug: https://bugs.launchpad.net/juju-core/+bug/1321442 I've analyzed the code and updated the bug with a rough plan to roll out support for the non-default VPC scenario on EC2. Unfortunately, juju supports either an EC2-Classic (no VPC) or EC2-VPC (only with a default VPC) at the moment. There are features planned and already in progress in feature branches that will allow greater control and flexibility with VPC deployments, so hopefully the situation will improve soon. Until then the proposed workaround - having a way to specify a "vpc-id" to use in environments.yaml needs to be implemented. So please use the quoted bug to track its progress and add your feedback on the proposal. Thanks, Dimiter On 13.07.2015 11:21, Mark Hannessen wrote: > Hi, > > For one of our customers we seek to deploy a juju setup inside of a > Amazon VPC. I have already configured the VPC with an internal > gateway and am able to boot machines inside of it as expected. > Internet connectivity works as expected. > > Unfortunately juju bootstrap does not seem to deploy the bootstrap > node inside the VPC by default. juju bootstrap --constraints > "cpu-cores=1" --upload-series trusty --upload-tools --to > zone=eu-west-1a > > I suspect i need a parameter to specify the subnet of the VPC > (subnet-06932f5f) but i couldn't find it on > https://jujucharms.com/docs/devel/config-general > > You can see my current configuration below. > > default: amazon > > environments: amazon: type: "ec2" region: "eu-west-1" access-key: > "" secret-key: "" image-stream: "released" > default-series: trusty > > > Anyone any idea as to how to make this work? > > Kind Regards, > > Mark > - -- Dimiter Naydenov Juju Core Sapphire team <http://juju.ubuntu.com> -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJVpPxWAAoJENzxV2TbLzHw/iIH/RWm8v9mHzpowfXrUPJidH1F Q6NfgpCm9DuFCLLcNUxMjmFOWD5/DkhcmDe/B8ib9NrE27Qd56qpCVLYxFWj/5xm QJ/ch4s5S2xlSFixH3423VFyDqY9EQ08Ftg8Q5wCkuCHGyEm5Cg1K+HcXduOsWaC Z7NE7+Arb9YOybUto3DSofg0Qs2WpQYhQkxBuwXyxUsYGYCYR0b14gZXlhJ5wqO9 9siUL/PxD7u1IwD+CZ5l3uGxi6MmEX0j1wLU6KGaOwOzutssTdn7/sEz3+Djw6Zj 3fJMjLitDFfBmZhXw6NKwlysB4045B3vpvrCGroFU0zg43NX6M7Cits8c9L2JuM= =DB/0 -END PGP SIGNATURE- -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: Container Networking
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Chuck, In 1.23.3 we landed an experimental addressable containers under a feature flag (address-allocation). It however still needs a MAAS that's able to give addresses over its API (maas profile ipaddresses reserve). It's not tested whether it will work if MAAS is not managing DHCP/DNS for its own nodes. I've added a comment on the bug to ask for more info from James. Cheers, Dimiter On 18.06.2015 23:22, Charles Butler wrote: > Greetings, > > If you missed today's Juju Office Hours - James showed up and asked > a great question with regard to LXC container networking on hosts. > For clarity he is not working on the local provider, he's using > juju deploy --to lxc:# on bare metal machines provisioned by MAAS. > A bug filed for the issue can be found here: > https://bugs.launchpad.net/juju-core/+bug/1466629 > > The MAAS region server (unmanaged) in his setup however, does not > manage the network of the machines. This particular network had an > existing DNS, and DHCP services - so it was not conclusive to let > MAAS control the networking with its own services. As I understand > it in the 1.23.x series of Juju, MAAS and AWS have landed support > for full networking, including cross host networking of > containers. > > This is not conclusive with what James has seen, can someone from > the team working on this take a look into this, and give a brief > status update as to where we are currently with supporting full > container addressability as well as any fix, or work around? > > Also I'd like to take this time to ask, if you're using juju and > containers in production, what good things, bad things have you > ecountered? > > Thanks, and all the best > > > > > > Charles Butler <mailto:charles.but...@canonical.com>> - Juju Charmer Come see the > future of datacenter orchestration: http://jujucharms.com > > - -- Dimiter Naydenov Juju Core Sapphire team <http://juju.ubuntu.com> -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJViDJNAAoJENzxV2TbLzHwLVEH/Rdn21XZ4mWj0pshJBC/SayK abhLY524iwmt1G/K8zF8PEicYCLR2edOSJ0ee8gmUH3rOC6Cz8ufsAi0y3wevl+j yo17dvGeDb63MtN1AJnZ+ApRaranXE6A2Rqg4sHeOlVSN3X1epVMLeJuQdOQ+25I KFDGMBfaJcUoOO8Qh9apHN3s94hb/7AQSJswHYPIgE6Nh4UMraJyjzbJTt3IfbSm Rz35fsrLwFDjEUbiLKMRji+nb1WnV4UnN8tIKoGX0hslYdB9LXkY7MQo+uzikCY2 G6KVjn8qqvB5cvzYmXVxnJmPYFA3iL5sFdMqSbUVBcywmD3F8yqKHtKlVThfTNc= =aNbz -END PGP SIGNATURE- -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: setup and configuration about "juju-br0"
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi shhan, Can you try using the latest release of Juju 1.23.3 - there were a few changes around juju-br0 and lots of issues were resolved. Hope this helps, Dimiter On 18.05.2015 17:53, shhan wrote: > hi all, > > I meet a trouble about setup and configuration of "juju-br0" on a > node of private MAAS environment. I try to bring up a Container > over a node, but failed with following messages. > > The problem is that I could find the configuration file of > juju-br0. any suggestions and help will be appreciated. > > -- > /var/lib/juju/containers/juju-machine-102-lxc-5/container.log: > > lxc-start 1431959506.073 ERRORlxc_conf - > conf.c:instantiate_veth:2978 - failed to attach 'veth9PAIYX' to > the bridge 'juju-br0': No such device lxc-start 1431959506.075 INFO > lxc_monitor - monitor.c:lxc_monitor_sock_name:177 - using monitor > sock name lxc/ad055575fe28ddd5//var/lib/lxc lxc-start > 1431959506.105 ERRORlxc_conf - conf.c:lxc_create_network:3261 - > failed to create netdev lxc-start 1431959506.105 ERRORlxc_start > - start.c:lxc_spawn:826 - failed to create the network > -- > > The output of "ifconfig " is: -- eth0 > Link encap:Ethernet HWaddr 00:25:90:88:bc:66 inet addr:10.0.0.102 > Bcast:10.0.0.255 Mask:255.255.255.0 inet6 addr: > fe80::225:90ff:fe88:bc66/64 Scope:Link UP BROADCAST RUNNING > MULTICAST MTU:1500 Metric:1 RX packets:265493 errors:0 dropped:0 > overruns:0 frame:0 TX packets:27886 errors:0 dropped:0 overruns:0 > carrier:0 collisions:0 txqueuelen:1000 RX bytes:24700318 (24.7 MB) > TX bytes:2804363 (2.8 MB) Memory:dfb2-dfb4 > > eth2 Link encap:Ethernet HWaddr 00:25:90:90:04:8d inet6 addr: > fe80::225:90ff:fe90:48d/64 Scope:Link UP BROADCAST RUNNING > MULTICAST MTU:1500 Metric:1 RX packets:218455 errors:0 dropped:0 > overruns:0 frame:0 TX packets:15 errors:0 dropped:0 overruns:0 > carrier:0 collisions:0 txqueuelen:1000 RX bytes:13981120 (13.9 MB) > TX bytes:1306 (1.3 KB) > > loLink encap:Local Loopback inet addr:127.0.0.1 > Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING > MTU:65536 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 > frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) > > lxcbr0Link encap:Ethernet HWaddr 3a:ef:2b:d5:88:9a inet > addr:10.0.1.1 Bcast:10.0.1.255 Mask:255.255.255.0 inet6 addr: > fe80::38ef:2bff:fed5:889a/64 Scope:Link UP BROADCAST RUNNING > MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 > overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 > carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX > bytes:648 (648.0 B) > > virbr0Link encap:Ethernet HWaddr f6:1b:ae:68:53:b6 inet > addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 UP > BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 > dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 > overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) > TX bytes:0 (0.0 B) > > > -- > > current cloud environment: MAAS: 1.7.3 juju-core: 1.23.2 node OS: > ubuntu 14.04.2 --- > > > Thanks, > > best, shuchu > > - -- Dimiter Naydenov Juju Core Sapphire team <http://juju.ubuntu.com> -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJVWxSMAAoJENzxV2TbLzHwg5AH/jws1lyH8L4aqOx8dGyhtmhW WquwnDNTVLo2+fdd1vhotFx4EhhwA4QgQclXaCdYutExVC7ePrPNwcyAHeiTJuCd uhGiBlgHWdzZ/Pp98vlbfRMGS690AG/9uzogqRhHuz1QQ8OMP6e0ea76XWAtCFYD AOgBEQn15FPcapDPPRFKfkyMo05PkT5x4DD3hw7v/CqSGGgntEtrOwiL0A/dgQB6 8VPeAIQqqI7duFMynw3WsKyYywNcGCgo1MsCaU7mgAJFW4qM0nQQ71pCK1dUVJ+m 0hl9OMZVF0GGy8bz6XoKB1oHwCj98eyvTKsGlKdRxRd68ujjxJdoytbMspX2V9I= =OSVg -END PGP SIGNATURE- -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: unit-get and ipv6 addresses
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I've asked Jake to file a bug for this issue, as it will be easier to track it and collect all the information in one place. In the mean time I'll be analyzing the possible cause for this. Cheers, Dimiter On 4.03.2015 17:13, Jake Kugel wrote: > Hi, > > we also got around it by disabling IPv6 on our hosts. > > I had tried sending additional logs Dimiter requested but the email > was too large for mailing list server. For lack of better idea on > how to deal with large attachments I had sent Dimiter logs directly > (sorry Dimiter). Maybe pastebin next time? > > Thanks, Jake > > > juju-boun...@lists.ubuntu.com wrote on 03/04/2015 04:03:09 AM: > >> From: "Thierry fa...@linux.vnet.ibm.com" >> To: juju@lists.ubuntu.com Date: >> 03/04/2015 04:03 AM Subject: Re: unit-get and ipv6 addresses Sent >> by: juju-boun...@lists.ubuntu.com >> >> Hello, >> >> I got a similar issue and solved it by disabling IPv6 under main >> host so > >> lxc containers could communicate through IPv4 and access to >> external > world. >> I haven't yet understand the issue but it sounds like if the main >> host is IPv6 enabled, then system tries to communicat through >> IPv6 even though IPv4 addresses are the only one configured. If >> anyone get an idea let me know. If you think that needs a bug let >> Jake or me know (at least) as we get concerned with the issue >> Thanks Thierry >> >> >> On 03/02/2015 04:03 PM, Dimiter Naydenov wrote: > Hi Jake, > > Thanks for the logs! However, I still can't find the reason this > should be happening just from those logs. Can you also send us the > unit logs from wordpress and mysql? A dump of "ifconfig -a" on each > of the machines should also be useful. > > Regards, Dimiter > > On 28.02.2015 00:42, Jake Kugel wrote: >>>>> Hi Dimiter, >>>>> >>>>> thanks, here are the files: >>>>> >>>>> Jake >>>>> >>>>> >>>>> >>>>> juju-boun...@lists.ubuntu.com wrote on 02/27/2015 02:58:01 >>>>> PM: >>>>> >>>>>> From: Dimiter Naydenov >>>>>> To: juju@lists.ubuntu.com Date: 02/27/2015 02:58 PM >>>>>> Subject: Re: unit-get and ipv6 addresses Sent by: >>>>>> juju-boun...@lists.ubuntu.com >>>>>> >>>>> Hi Jake, >>>>> >>>>> Can you provide some more information: - your >>>>> environments.yaml file - machine-0.log, machine-1.log, and >>>>> machine-2.log from /var/log/juju/ on each machine Before >>>>> sending these, please make a quick check to remove any >>>>> sensitive info from the files (e.g. access/secret keys, >>>>> password, etc.) >>>>> >>>>> You can get the logs by using "juju ssh 0" (or 1 and 2 for >>>>> the other machines) to connect, run chown a+r >>>>> /var/log/juju/machine*.log, then log back out and use "juju >>>>> scp 0:/var/log/juju/machine-0.log ~/" (again replace 0 with >>>>> 1 or 2). >>>>> >>>>> Thanks! Dimiter >>>>> >>>>> On 27.02.2015 22:19, Jake Kugel wrote: >>>>>>>> Hi, >>>>>>>> >>>>>>>> I am using juju 1.21.1-trusty-i386 and deploying to a >>>>>>>> manual environment, and had a problem deploying >>>>>>>> wordpress following the getting started page here >>>>>>>> [1]. When I tried to view wordpress with a browser >>>>>>>> it gave me an "Error establishing a database >>>>>>>> connection", and from a little bit of digging found >>>>>>>> that wordpress was configured with an ipv6 address >>>>>>>> for the mysql host. Switching this manually to the >>>>>>>> ipv4 address fixed the problem. >>>>>>>> >>>>>>>> Assuming for a minute that wordpress doesn't support >>>>>>>> ipv6, is there a way to avoid having it configured >>>>>>>> with an ipv6 address? I see that unit-get >>>>>>>> private-address is returning the ipv6 address for the >>>>>>>> mysql host, is that normal behavior? On the mysql >>>>>>>> host mac
Re: unit-get and ipv6 addresses
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Jake, Thanks for the logs! However, I still can't find the reason this should be happening just from those logs. Can you also send us the unit logs from wordpress and mysql? A dump of "ifconfig -a" on each of the machines should also be useful. Regards, Dimiter On 28.02.2015 00:42, Jake Kugel wrote: > Hi Dimiter, > > thanks, here are the files: > > Jake > > > > juju-boun...@lists.ubuntu.com wrote on 02/27/2015 02:58:01 PM: > >> From: Dimiter Naydenov To: >> juju@lists.ubuntu.com Date: 02/27/2015 02:58 PM Subject: Re: >> unit-get and ipv6 addresses Sent by: >> juju-boun...@lists.ubuntu.com >> > Hi Jake, > > Can you provide some more information: - your environments.yaml > file - machine-0.log, machine-1.log, and machine-2.log from > /var/log/juju/ on each machine Before sending these, please make a > quick check to remove any sensitive info from the files (e.g. > access/secret keys, password, etc.) > > You can get the logs by using "juju ssh 0" (or 1 and 2 for the > other machines) to connect, run chown a+r > /var/log/juju/machine*.log, then log back out and use "juju scp > 0:/var/log/juju/machine-0.log ~/" (again replace 0 with 1 or 2). > > Thanks! Dimiter > > On 27.02.2015 22:19, Jake Kugel wrote: >>>> Hi, >>>> >>>> I am using juju 1.21.1-trusty-i386 and deploying to a manual >>>> environment, and had a problem deploying wordpress following >>>> the getting started page here [1]. When I tried to view >>>> wordpress with a browser it gave me an "Error establishing a >>>> database connection", and from a little bit of digging found >>>> that wordpress was configured with an ipv6 address for the >>>> mysql host. Switching this manually to the ipv4 address >>>> fixed the problem. >>>> >>>> Assuming for a minute that wordpress doesn't support ipv6, is >>>> there a way to avoid having it configured with an ipv6 >>>> address? I see that unit-get private-address is returning >>>> the ipv6 address for the mysql host, is that normal behavior? >>>> On the mysql host machine log, I see this: >>>> >>>> 2015-02-27 14:56:59 INFO juju.worker.machiner machiner.go:94 >>>> setting addresses for machine-2 to ["local-machine:127.0.0.1" >>>> "public:9.114.192.29" "local-machine:::1" >>>> "local-cloud:fd55:faaf:e1ab:38d:944a:7931:9b4c:c621" >>>> "local-cloud:fd55:faaf:e1ab:38d:a8c0:f5da:7109:1e67" >>>> "local-cloud:fd55:faaf:e1ab:38d:f816:3eff:fee2:f0fc"] >>>> >>>> Thanks in advance for any advice, Jake Kugel >>>> >>>> [1] https://jujucharms.com/docs/getting-started >>>> >>>> > > >> >> -- Juju mailing list Juju@lists.ubuntu.com Modify settings or >> unsubscribe at: https://lists.ubuntu.com/mailman/ listinfo/juju >> >> >> - -- Dimiter Naydenov Juju Core Sapphire team <http://juju.ubuntu.com> -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJU9Hu9AAoJENzxV2TbLzHwha4H/0s+UUZr5Z2ov4TcjAIT93cb I/JqHcpo1ynvOyGCv5/VD801RHnwDi+tWpoKJtUmgQ6PTV8iW78U7C55MgcXsTmz PKh3Bl5O8IN2oVF3SbVD7jc8P70wtbucIVsml1lsb34TCgJFSA1rJ2R7SrnUMtiE EXNg455jS84aDiJW+Lw8glXHB1X3f+Kv7jnKN2Bksza+z4T8+hxa7HLc8qCdozD7 MoEVLoJO/75LYVjYCMhqZhkqCUb5T8gvdVcb2zdIOnhk63A+G0FQSPUrvTps3cfv iCmD1nXUyufFV5FB3ks9nwtlrGjpsAcbJJu0NCwJ9VCOQjxvGXjTYksJNUi8VbU= =lBiY -END PGP SIGNATURE- -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: unit-get and ipv6 addresses
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Jake, Can you provide some more information: - - your environments.yaml file - - machine-0.log, machine-1.log, and machine-2.log from /var/log/juju/ on each machine Before sending these, please make a quick check to remove any sensitive info from the files (e.g. access/secret keys, password, etc.) You can get the logs by using "juju ssh 0" (or 1 and 2 for the other machines) to connect, run chown a+r /var/log/juju/machine*.log, then log back out and use "juju scp 0:/var/log/juju/machine-0.log ~/" (again replace 0 with 1 or 2). Thanks! Dimiter On 27.02.2015 22:19, Jake Kugel wrote: > Hi, > > I am using juju 1.21.1-trusty-i386 and deploying to a manual > environment, and had a problem deploying wordpress following the > getting started page here [1]. When I tried to view wordpress with > a browser it gave me an "Error establishing a database connection", > and from a little bit of digging found that wordpress was > configured with an ipv6 address for the mysql host. Switching this > manually to the ipv4 address fixed the problem. > > Assuming for a minute that wordpress doesn't support ipv6, is there > a way to avoid having it configured with an ipv6 address? I see > that unit-get private-address is returning the ipv6 address for the > mysql host, is that normal behavior? On the mysql host machine log, > I see this: > > 2015-02-27 14:56:59 INFO juju.worker.machiner machiner.go:94 > setting addresses for machine-2 to ["local-machine:127.0.0.1" > "public:9.114.192.29" "local-machine:::1" > "local-cloud:fd55:faaf:e1ab:38d:944a:7931:9b4c:c621" > "local-cloud:fd55:faaf:e1ab:38d:a8c0:f5da:7109:1e67" > "local-cloud:fd55:faaf:e1ab:38d:f816:3eff:fee2:f0fc"] > > Thanks in advance for any advice, Jake Kugel > > [1] https://jujucharms.com/docs/getting-started > > - -- Dimiter Naydenov Juju Core Sapphire team <http://juju.ubuntu.com> -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJU8NpZAAoJENzxV2TbLzHw5NsH/1CB0KtyasUJaLaaDbumTGER qnaU6GJRvUtvFyt0RUorHdVVdnVrr120G/0Gf7gqmMdI37J5G6InBok2Zh1wl6We 2N6WH7uKDPSDINQJJqS2tXoSnp12924U4DCoC5ceRdkZuLhmHfMkWv3uj+nPOk9D YmwKEnKNRxiY4nCZwIDpO5wJUuy25dSQJH3OIBJZbu56VB18bQhDt8SVmk0ph/B+ guBkMq/i5+Fe+i9cRLk8Hq5HTOreYocOOwkFKmui5ZDmDSRvqtD3sg7DJvKrH5qx CmNkQJ8xzCY1SX+VzeXmxBXWEX+scdS5vLgKoJ3YcneYIQWFUag1bfmRA+qfcvA= =sId2 -END PGP SIGNATURE- -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: python-django charm and absent python-yaml package
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hey Vahric, Please, file a bug here: https://bugs.launchpad.net/charms/+source/python-django This is indeed the right place to report issues with charms. So far I can't see this exact issue reported. Thanks, Dimiter On 16.01.2015 11:38, Vahric Muhtaryan wrote: > > Hello All > > Newly i tried to install the python-django charm. Installation is > failed, when i debug i saw that python-yaml package is not > installed after manually install it i can resubmit the charm > deployment and its succeed . > > Looks like Patrick Hetu is the maintainer , is this list right > place to inform such things ? i would like to ask do you aware > about such issue ? > > Regards Vahric Muhtaryan > > > > > - -- Dimiter Naydenov juju-core team -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJUuOGdAAoJENzxV2TbLzHwivUH+QHD0iemGnNS7/MM3Zr0OcJk qdIqRAP6faYviQC/LcQWr+e42S2WQPy71viJzAbhJ8o2ieUIJ4pFzwwJzuTdDJkh ZUYGroENP5b6CvVrQ+hwhsh4sYNGENVoejkr4Ab0lxTy/M4B6arLiAVmqcm1w3pk W6gwxEikRVGGpPvfviGOP0+ZhgaVBsrrK5b5QeDyC/egfRj+X4CGHX43VQWwPY9Z SeLSYvA3kHYhOKrXWk8l4+kfLSeJ+vlaEn0EkcT8AVDRkkL2xH9pcCeLFuncPDv7 FB+aXpmrqFnVuGcYu57+7gF8UOl9kS9EE9ZDvilVRYHsyepQNuwyDiklXWa7R48= =VbKb -END PGP SIGNATURE- -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: About bootstrap server , size and dedicate or share it for applications or not
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > 1.- I have been able to use a 613MB RAM server for a development > environment, but a 1GB RAM server is recommended. You should also ensure the machine has enough disk space for the MongoDB database, which IIRC by default is configured to pre-allocate 48MB (for 32-bit architectures), 183MB (for 64-bit OS X), or 512MB (for Windows) as minimum oplog size, and up to 1GB (on Linux) as maximum oplog size. Additionally, if you store a lot of cached images (for LXC containers) or other binaries (juju tarballs, "fat" charms, etc.) the MongoDB database will grow. > 2.- Yes, it is allowed but not recommended. You can deploy > additional server to that machine specifying "--to 0" when > deploying. However, this is not recommended because the service > will eat up RAM. Another option is to deploy services isolated in LXC containers, with - --to lxc:<#> where <#> is a juju machine ID (0 for the bootstrap node). > 3.- You can, but only if you are using the local provider. If you > are going to use a cloud environment, then the bootstrap node needs > to be in that same environment. Alternatively, you could bootstrap a manual environment on the Ubuntu desktop machine, but then you'll have to add manually each additional machine to the environment, with add-machine ssh:@ - e.g. $ juju add-machine myuser@192.168.1.123 - -- Dimiter Naydenov juju-core team -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJUt9rSAAoJENzxV2TbLzHw5sMH/RPUJolTvImGI8zoY4Aleugq ESBMh4B6S3befBdo920Hw9k0QAxLdyAJiPRccmRYiecd5/djv14LlpUGRyxuxhoM GsVFgVAR/cFBsjAjxPX1EMKK5jvm0jSAp+zJbaWoJt9toolZ10Mi0sNx7wEvPy7M dkJI0jD2J2U16ch7R3YVngXBckQEGafxLo3aJHOGYZT2ENfs4yjo+fIHxh2xZJ/h uWlRKEb3vd23HPYLP43EFvZELCujg3uFyxCch0HVw/XFMc2G4DdZN4bANZhcnHud fsdsldnpHaf2O1UkYnzfJudFwML6BHVQxVmJQUPdyxTyRC0rdFMve5rJWOKfCsc= =k40X -END PGP SIGNATURE- -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: Question regarding --upload-tools and implications
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 >> 4) IIRC we use the version of the juju client when we upload, not >> the version of the jujud binary. Eg if you happen to have a 1.22 >> jujud on your system but you use a 1.23-beta2 client we'll >> upload it but call it 1.23.0.1-beta2. From there upgrades etc >> will be very confused. > > I suspect this is true. A development client can make surprising > decisions when upgrading a stable environment. > It is true because --upload-tools forces the built tarball to *lie* about its actual version. So even though you might actually have 1.20.x binaries inside the tarball (e.g. left in your $PATH from before) --upload-tool prepares, it will *appear* as they are x.y.z.1, where x.y.z is your juju client's version (or when you have the source - - the value of Current in version/version.go). Beware. - -- Dimiter Naydenov juju-core team -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJUt9dVAAoJENzxV2TbLzHwjNUIAJQXyDeQCywDp4vCKLquTSLF ZAY/Z6GJ/yF0ptYyiECVPuBjnzIQXMKxXfPYAQmFBTyWeb+mOljnGS8oGr3Nem7N lIGuPHGUU0VNJLVRau+JjxTp89BEUR5eNKtQnmzPlU2ZyceSx5DuPnQ4H/uvmJsj Xrb/KzVpwNn5K4hlw+d0ZPzZOA0hCKUXJYK04gUT6+rnYiQP2Ek8ywxrbGs6sQ9J LznQ1ZxwlIcgF2Y0e6WycomiR52lOBL/LK8/IL4OHCXlIYai34LTLUDU2uH8CRF0 v6zYxyPuvsKZ/pLxPtTxxYs8HB7nOHZawQ7pI+qO94KS7fDi+O0ntFR66n8k4YY= =h2in -END PGP SIGNATURE- -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Goamz Migrated to GitHub!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, There was an ongoing discussion to migrate https://launchpad.net/goamz to GitHub. I'm happy to announce this has happened today - please find the new repository at: https://github.com/go-amz/amz Import paths have changed to use the http://gopkg.in/ format: Before it used to be: import "launchpad.net/goamz/ec2" Now it becomes: import "gopkg.in/amz.v1/ec2" Bug reporting will remain on Launchpad, as well as an archive of the old source code. The migration was performed with full history preservation. The goamz users group (https://groups.google.com/forum/#!forum/goamz) was also notified of the change. Check out the repository page for links and more information. Have a nice weekend and enjoy! :) - -- Dimiter Naydenov juju-core team -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJUiya7AAoJENzxV2TbLzHwvQ4IAMSeXIfR+rlS2Z3Otu1JrMOX Aehdj3clf3/qkl3k77io/hhOGKhMWT96y3O4HxolAzXCJGg9umSBUIVh5Yj9z6B3 YFBtG5+UH4KY/z1rd6KZFjw2IEOsDS3uCCRbA7yrtvDMcOnpIo/AjyUyC4NYZ+si OKpJ/L6nAFK+kkKu7WwRXuRJwCQ2tGELYB8UXBft274NwCwXj6a+ejI9tjsxkm4S JJw5Va0TXheM6MNRcWG6SW7rdmOOG+TwN/duffBh8XAxHdmu0mTjxxW2pY+W1HGD CUjMmiMARuyTuMfeeN4MfjLF4uEnUctpOcVe6XdE43m8rktKf/HYwo5V0rArHXo= =nTL8 -END PGP SIGNATURE- -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: Multiple networks with JUJU and 3rd party Cinder integration.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 25.10.2014 03:13, Mark Shuttleworth wrote: > On 24/10/14 15:28, Nate dell wrote: >> I'll look at binding specific cdrs to the openstack charms. It >> sounds like your suggesting using a configuration management >> system like salt, ansible, puppet, or chef in conjunction with >> juju. Ansible is setup at the client so will look to integrate >> the two, was reluctant to do that out of fears they would step on >> each other. The IRC channel has been very helpful in providing >> suggestions on how to proceed on the cinder side. Hey Nate, Thanks for considering Juju for your scenario! > > The different systems can easily be made to be polite to one > another :) > > In a little while you'll be able to specify a charm to put on > every machine, or groups of machine, and that will probably be a > cleaner way to handle the baseline machine setup. > > Mark > In the mean-time, until Juju starts to provide this feature, you can consider a workaround. It looks like all openstack charms can have a subordinate unit (on the same machine) via the hacluster relation. If you write a shared subordinate charm, deploy it, and relate it to the openstack services you need to configure, you can have the same code executing on each machine. I hope this helps, - -- Dimiter Naydenov juju-core team -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJUS909AAoJENzxV2TbLzHw7qoH/3T1fxB1ugJ5cJUTGvlPIF6p BPq0xe3VwS82aCFDEbZZMwOsWhb8IlWtcuDTc0kS0zJRm5ZVwq0CZq5tIIYC30+V pDmKBqGup8O6W8WyqWv80vssUOFt1gfMhL8OrRNJO/pklXD7J4i9qDiIx/Y3dYBu vQBh8RbHZ0V/mESQ7yMgrJ1k9KdbvTLxpnUk5m+J2EfBAGfGbWZEdSeakGPb6DSo yebmR1ThI0AP+srxx1mlDUo6p0MbNXe4VXlDu2oG8nOJg7A6sYKuCyYICO4lgq3p gomxILNLHARCPY0O8tjNqQAiykW+OxdzxE1v0pb96xVnIrjpe1h50Ba3qrDwvX4= =dhJp -END PGP SIGNATURE- -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: add-machine and add-unit to this machine
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Juju CLI won't give you the machine ID in a script-friendly format, so you have 2 options: 1) Use juju-deployer, which supports complex, scripted deployments with juju and offers a lot of customization and tunning. Docs: http://pythonhosted.org/juju-deployer/ Source: https://launchpad.net/juju-deployer (you can apt-get install juju-deployer) 2) In you script, parse the output of juju add-machine to extract the machine ID from the "created machine XXX" string an use it. I hope this helps! On 6.08.2014 15:15, Ilisia Felane wrote: > Yes, ok, I know do that manually. but for a script, I try to create > a new machine and install over an entire service. Without having to > know the number of the machine. This seems possible MaaS creating a > machine with a tag, but not implemented for the Cloud. > > My question is how can I create a machine identified under a > certain name and install it as a service you need via this > identifier. > > > 2014-08-06 13:34 GMT+02:00 John Meinel <mailto:j...@arbash-meinel.com>>: > > When you do "juju add-machine" it should print out a line like: > created machine 10 > > You should be able to then do: juju add-unit SERVICE --to 10 > > John =:-> > > > > - -- Dimiter Naydenov juju-core team -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJT4h7tAAoJENzxV2TbLzHwd2sH/RUR4XZLHZH6R8oXqzCMnixP zUSt5IrzLFfsSaNRpzlEP63JWEmGgJpSOVudBTF8mug/7DYhAmHGc+Usyn/JPMIg RR77x3nonB2OBRmLjKcaw1mWY6Tqxpdy9gdepE/bxygi4vY68mNd1hBQaVGAtsrE fDCgPFFHDhrMXXu5t5EUZdfJzgUlf/GYC9wJnKB3RyyKsgGRSXWu2Wq2bKtBdpr8 SdRLphOul4iE5KquRrnUb+bqoBolL/Sw94lITw6nTWYQRo9E6abvfNxPnUhVKxd9 gCxrKfIVlQJiZBWSOzZUl7GyP8y8Dp8C56UFFORVGuIk4UKXxRy9rn9y0fcTzl4= =JoBu -END PGP SIGNATURE- -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: Juju on Reddit
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hey Matty, I'm dimitern on reddit, and I'll be glad to help with moderation or questions, etc., as I regularly visit AskUbuntu as well. Cheers, Dimiter On 20.05.2014 18:25, Matthew Williams wrote: - -- Dimiter Naydenov juju-core team -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTfFp2AAoJENzxV2TbLzHwRNwH/A2+I7vkI51AqEaYcExvwkLH CkD9oxiCnND0yNdKzaqn6uihsyU/WPcorvRP3DJKHIzRyP+10NIcooSjTboD9LrZ jshKIulT7gnysExzkn1BJxsNer12hqd9CEiillZeiwOtuFnuJvfvvEwXi1+TW5PQ lkmQNkrJh9y3ZWEAmXVEHXIDr808Hrsj9qsBqgkIDkuenwFB6mtf+ZecKTTjlNaP ZPRfA9SPkDN5TN7QNpEo2pooZxE3agxxPDy2xvRM0Uc2WdMW+7i1sju46XTonpjE OqscRwrpXqWyd/Y57TO8r2ugJ0pVIBjoY1S/9qr+aB+qqlbUwaNjWENCLv4flvc= =riTD -END PGP SIGNATURE- -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: Juju on Reddit
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hey Matty, I'm dimitern on reddit, and I'll be glad to help with moderation or questions, etc., as I regularly visit AskUbuntu as well. Cheers, Dimiter On 20.05.2014 18:25, Matthew Williams wrote: > Hi Folks, > > We now have a subreddit for posting topics about juju: > > http://www.reddit.com/r/juju > > I'm looking for volunteers who would like to help with being > moderators. > > Feel free to start posting links > > Thanks > > Matty > > - -- Dimiter Naydenov juju-core team -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTfFp2AAoJENzxV2TbLzHwRNwH/A2+I7vkI51AqEaYcExvwkLH CkD9oxiCnND0yNdKzaqn6uihsyU/WPcorvRP3DJKHIzRyP+10NIcooSjTboD9LrZ jshKIulT7gnysExzkn1BJxsNer12hqd9CEiillZeiwOtuFnuJvfvvEwXi1+TW5PQ lkmQNkrJh9y3ZWEAmXVEHXIDr808Hrsj9qsBqgkIDkuenwFB6mtf+ZecKTTjlNaP ZPRfA9SPkDN5TN7QNpEo2pooZxE3agxxPDy2xvRM0Uc2WdMW+7i1sju46XTonpjE OqscRwrpXqWyd/Y57TO8r2ugJ0pVIBjoY1S/9qr+aB+qqlbUwaNjWENCLv4flvc= =riTD -END PGP SIGNATURE- -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
