Re: juju deploy with a series
The patch and instructions are listed here: https://github.com/juju/juju/pull/6954 We didn't go this route. In our project, we ended up using MAAS to provision CentOS node to test charms. On 06/15/2017 10:51 PM, fengxia wrote: +1 On 06/15/2017 10:47 PM, Andrew Wilkins wrote: On Fri, Jun 16, 2017 at 1:36 AM John Meinel <j...@arbash-meinel.com <mailto:j...@arbash-meinel.com>> wrote: "juju show-machine 10" is likely to tell you why we are failing to provision the machine. My guess is that we acctually need the alias to be "juju/centos7/amd64" for Juju to recognize that it is the container image we want to be starting. Also, the centos7 image from linuxcontainers.org <http://linuxcontainers.org> is not suitable for Juju to use. See https://bugs.launchpad.net/juju/+bug/1495978/comments/21. (We really need to publish the image, so people don't have to do this.) John =:-> On Thu, Jun 15, 2017 at 8:37 PM, Daniel Bidwell <drbidw...@gmail.com <mailto:drbidw...@gmail.com>> wrote: I am trying to deploy a charm that I am writing for both ubuntu and centos. "lxc image alias list" produces: lxc image alias list +---+--+---+ | ALIAS | FINGERPRINT |DESCRIPTION| +---+--+---+ | centos7 | 41c7bb494bbd | centos7 | +---+--+---+ | juju/xenial/amd64 | 1e59027d1d58 | juju/xenial/amd64 | +---+--+---+ | ubuntu-xenial | 1e59027d1d58 | ubuntu-xenial | +-------+--+-------+ "juju deploy ~/charms/xenial/aubase1 --series centos7 aubasecentos" looks like it is starting, but a "juju status" produces: juju status ModelController Cloud/Region Version default lxd-testlocalhost/localhost 2.1.2 App Version Status Scale CharmStore Rev OS Notes aubase1active 1 aubase1 local5 ubuntu aubasecentos waiting0/1 aubase1 local4 centos UnitWorkload Agent Machine Public address Ports Message aubase1/4* activeidle910.130.54.192 aubasecentos/4 waiting allocating 10 waiting for machine Machine StateDNSInst idSeries AZ 9started 10.130.54.192 juju-a0c4c9-9 xenial 10 downpendingcentos7 What do I need to do to deploy a centos lxd container with my charm? -- Daniel Bidwell <drbidw...@gmail.com <mailto:drbidw...@gmail.com>> -- Juju mailing list Juju@lists.ubuntu.com <mailto:Juju@lists.ubuntu.com> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju -- Juju mailing list Juju@lists.ubuntu.com <mailto:Juju@lists.ubuntu.com> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju -- Feng xia Engineer Lenovo USA Phone: 5088011794 fx...@lenovo.com Lenovo.com Twitter | Facebook | Instagram | Blogs | Forums -- Feng xia Engineer Lenovo USA Phone: 5088011794 fx...@lenovo.com Lenovo.com Twitter | Facebook | Instagram | Blogs | Forums -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: juju deploy with a series
+1 On 06/15/2017 10:47 PM, Andrew Wilkins wrote: On Fri, Jun 16, 2017 at 1:36 AM John Meinel <j...@arbash-meinel.com <mailto:j...@arbash-meinel.com>> wrote: "juju show-machine 10" is likely to tell you why we are failing to provision the machine. My guess is that we acctually need the alias to be "juju/centos7/amd64" for Juju to recognize that it is the container image we want to be starting. Also, the centos7 image from linuxcontainers.org <http://linuxcontainers.org> is not suitable for Juju to use. See https://bugs.launchpad.net/juju/+bug/1495978/comments/21. (We really need to publish the image, so people don't have to do this.) John =:-> On Thu, Jun 15, 2017 at 8:37 PM, Daniel Bidwell <drbidw...@gmail.com <mailto:drbidw...@gmail.com>> wrote: I am trying to deploy a charm that I am writing for both ubuntu and centos. "lxc image alias list" produces: lxc image alias list +---+--+---+ | ALIAS | FINGERPRINT |DESCRIPTION| +---+--+---+ | centos7 | 41c7bb494bbd | centos7 | +---+--+---+ | juju/xenial/amd64 | 1e59027d1d58 | juju/xenial/amd64 | +---+--+---+ | ubuntu-xenial | 1e59027d1d58 | ubuntu-xenial | +-------+--+-------+ "juju deploy ~/charms/xenial/aubase1 --series centos7 aubasecentos" looks like it is starting, but a "juju status" produces: juju status ModelController Cloud/Region Version default lxd-testlocalhost/localhost 2.1.2 App Version Status Scale CharmStore Rev OS Notes aubase1active 1 aubase1 local5 ubuntu aubasecentos waiting0/1 aubase1 local4 centos UnitWorkload Agent Machine Public address Ports Message aubase1/4* activeidle910.130.54.192 aubasecentos/4 waiting allocating 10 waiting for machine Machine StateDNSInst idSeries AZ 9started 10.130.54.192 juju-a0c4c9-9 xenial 10 downpendingcentos7 What do I need to do to deploy a centos lxd container with my charm? -- Daniel Bidwell <drbidw...@gmail.com <mailto:drbidw...@gmail.com>> -- Juju mailing list Juju@lists.ubuntu.com <mailto:Juju@lists.ubuntu.com> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju -- Juju mailing list Juju@lists.ubuntu.com <mailto:Juju@lists.ubuntu.com> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju -- Feng xia Engineer Lenovo USA Phone: 5088011794 fx...@lenovo.com Lenovo.com Twitter | Facebook | Instagram | Blogs | Forums -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: juju deploy with a series
There was a bug filed back in 2015: https://bugs.launchpad.net/juju/+bug/1495978 It has information on how to make a work around to run CentOS in LXD. On 06/15/2017 12:37 PM, Daniel Bidwell wrote: I am trying to deploy a charm that I am writing for both ubuntu and centos. "lxc image alias list" produces: lxc image alias list +---+--+---+ | ALIAS | FINGERPRINT |DESCRIPTION| +---+--+---+ | centos7 | 41c7bb494bbd | centos7 | +---+--+---+ | juju/xenial/amd64 | 1e59027d1d58 | juju/xenial/amd64 | +---+--+---+ | ubuntu-xenial | 1e59027d1d58 | ubuntu-xenial | +---+--+---+ "juju deploy ~/charms/xenial/aubase1 --series centos7 aubasecentos" looks like it is starting, but a "juju status" produces: juju status ModelController Cloud/Region Version default lxd-testlocalhost/localhost 2.1.2 App Version Status Scale CharmStore Rev OS Notes aubase1active 1 aubase1 local5 ubuntu aubasecentos waiting0/1 aubase1 local4 centos UnitWorkload Agent Machine Public address Ports Message aubase1/4* activeidle910.130.54.192 aubasecentos/4 waiting allocating 10 waiting for machine Machine StateDNSInst idSeries AZ 9started 10.130.54.192 juju-a0c4c9-9 xenial 10 downpendingcentos7 What do I need to do to deploy a centos lxd container with my charm? -- Feng xia Engineer Lenovo USA Phone: 5088011794 fx...@lenovo.com Lenovo.com Twitter | Facebook | Instagram | Blogs | Forums -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: juju deploy with a series
On Fri, Jun 16, 2017 at 1:36 AM John Meinel <j...@arbash-meinel.com> wrote: > "juju show-machine 10" is likely to tell you why we are failing to > provision the machine. > > My guess is that we acctually need the alias to be "juju/centos7/amd64" > for Juju to recognize that it is the container image we want to be starting. > Also, the centos7 image from linuxcontainers.org is not suitable for Juju to use. See https://bugs.launchpad.net/juju/+bug/1495978/comments/21. (We really need to publish the image, so people don't have to do this.) > John > =:-> > > > On Thu, Jun 15, 2017 at 8:37 PM, Daniel Bidwell <drbidw...@gmail.com> > wrote: > >> I am trying to deploy a charm that I am writing for both ubuntu and >> centos. "lxc image alias list" produces: >> >> lxc image alias list >> +---+--+---+ >> | ALIAS | FINGERPRINT |DESCRIPTION| >> +---+--+---+ >> | centos7 | 41c7bb494bbd | centos7 | >> +---+--+---+ >> | juju/xenial/amd64 | 1e59027d1d58 | juju/xenial/amd64 | >> +---+--+-------+ >> | ubuntu-xenial | 1e59027d1d58 | ubuntu-xenial | >> +---+--+---+ >> >> "juju deploy ~/charms/xenial/aubase1 --series centos7 aubasecentos" >> looks like it is starting, but a "juju status" produces: >> >> juju status >> ModelController Cloud/Region Version >> default lxd-testlocalhost/localhost 2.1.2 >> >> App Version Status Scale CharmStore Rev OS Notes >> aubase1active 1 aubase1 local5 ubuntu >> aubasecentos waiting0/1 aubase1 local4 centos >> >> UnitWorkload Agent Machine Public >> address Ports Message >> aubase1/4* activeidle910.130.54.192 >> aubasecentos/4 waiting allocating 10 waiting >> for machine >> >> Machine StateDNSInst idSeries AZ >> 9started 10.130.54.192 juju-a0c4c9-9 xenial >> 10 downpendingcentos7 >> >> What do I need to do to deploy a centos lxd container with my charm? >> -- >> Daniel Bidwell <drbidw...@gmail.com> >> >> >> -- >> 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 > -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: juju deploy with a series
John, There are multiple issues with this since we have just gone through a similar effort: 1. LXD does not support CentOS image. 2. Default "charm build" will produce a dist that will not run on CentOS, even with "--series centos7". On 06/15/2017 01:34 PM, John Meinel wrote: "juju show-machine 10" is likely to tell you why we are failing to provision the machine. My guess is that we acctually need the alias to be "juju/centos7/amd64" for Juju to recognize that it is the container image we want to be starting. John =:-> On Thu, Jun 15, 2017 at 8:37 PM, Daniel Bidwell <drbidw...@gmail.com <mailto:drbidw...@gmail.com>> wrote: I am trying to deploy a charm that I am writing for both ubuntu and centos. "lxc image alias list" produces: lxc image alias list +---+--+---+ | ALIAS | FINGERPRINT |DESCRIPTION| +---+--+---+ | centos7 | 41c7bb494bbd | centos7 | +---+--+---+ | juju/xenial/amd64 | 1e59027d1d58 | juju/xenial/amd64 | +---+--+---+ | ubuntu-xenial | 1e59027d1d58 | ubuntu-xenial | +-------+--+---+ "juju deploy ~/charms/xenial/aubase1 --series centos7 aubasecentos" looks like it is starting, but a "juju status" produces: juju status ModelController Cloud/Region Version default lxd-test localhost/localhost 2.1.2 App Version Status Scale CharmStore Rev OS Notes aubase1active 1 aubase1 local5 ubuntu aubasecentos waiting0/1 aubase1 local4 centos UnitWorkload Agent Machine Public address Ports Message aubase1/4* active idle910.130.54.192 aubasecentos/4 waiting allocating 10 waiting for machine Machine StateDNSInst idSeries AZ 9started 10.130.54.192 juju-a0c4c9-9 xenial 10 downpendingcentos7 What do I need to do to deploy a centos lxd container with my charm? -- Daniel Bidwell <drbidw...@gmail.com <mailto:drbidw...@gmail.com>> -- Juju mailing list Juju@lists.ubuntu.com <mailto:Juju@lists.ubuntu.com> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju <https://lists.ubuntu.com/mailman/listinfo/juju> -- Feng xia Engineer Lenovo USA Phone: 5088011794 fx...@lenovo.com Lenovo.com Twitter | Facebook | Instagram | Blogs | Forums -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: juju deploy with a series
"juju show-machine 10" is likely to tell you why we are failing to provision the machine. My guess is that we acctually need the alias to be "juju/centos7/amd64" for Juju to recognize that it is the container image we want to be starting. John =:-> On Thu, Jun 15, 2017 at 8:37 PM, Daniel Bidwell <drbidw...@gmail.com> wrote: > I am trying to deploy a charm that I am writing for both ubuntu and > centos. "lxc image alias list" produces: > > lxc image alias list > +---+--+---+ > | ALIAS | FINGERPRINT |DESCRIPTION| > +---+--+---+ > | centos7 | 41c7bb494bbd | centos7 | > +---+--+---+ > | juju/xenial/amd64 | 1e59027d1d58 | juju/xenial/amd64 | > +---+--+---+ > | ubuntu-xenial | 1e59027d1d58 | ubuntu-xenial | > +---+------+---+ > > "juju deploy ~/charms/xenial/aubase1 --series centos7 aubasecentos" > looks like it is starting, but a "juju status" produces: > > juju status > ModelController Cloud/Region Version > default lxd-testlocalhost/localhost 2.1.2 > > App Version Status Scale CharmStore Rev OS Notes > aubase1active 1 aubase1 local5 ubuntu > aubasecentos waiting0/1 aubase1 local4 centos > > UnitWorkload Agent Machine Public > address Ports Message > aubase1/4* activeidle910.130.54.192 > aubasecentos/4 waiting allocating 10 waiting > for machine > > Machine StateDNSInst idSeries AZ > 9started 10.130.54.192 juju-a0c4c9-9 xenial > 10 downpendingcentos7 > > What do I need to do to deploy a centos lxd container with my charm? > -- > Daniel Bidwell <drbidw...@gmail.com> > > > -- > 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
juju deploy with a series
I am trying to deploy a charm that I am writing for both ubuntu and centos. "lxc image alias list" produces: lxc image alias list +---+--+---+ | ALIAS | FINGERPRINT |DESCRIPTION| +---+--+---+ | centos7 | 41c7bb494bbd | centos7 | +---+--+---+ | juju/xenial/amd64 | 1e59027d1d58 | juju/xenial/amd64 | +---+--+---+ | ubuntu-xenial | 1e59027d1d58 | ubuntu-xenial | +---+--+---+ "juju deploy ~/charms/xenial/aubase1 --series centos7 aubasecentos" looks like it is starting, but a "juju status" produces: juju status ModelController Cloud/Region Version default lxd-testlocalhost/localhost 2.1.2 App Version Status Scale CharmStore Rev OS Notes aubase1active 1 aubase1 local5 ubuntu aubasecentos waiting0/1 aubase1 local4 centos UnitWorkload Agent Machine Public address Ports Message aubase1/4* activeidle910.130.54.192 aubasecentos/4 waiting allocating 10 waiting for machine Machine StateDNSInst idSeries AZ 9started 10.130.54.192 juju-a0c4c9-9 xenial 10 downpendingcentos7 What do I need to do to deploy a centos lxd container with my charm? -- Daniel Bidwell <drbidw...@gmail.com> -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju