Re: vsphere support

2017-10-05 Thread Andrew Wilkins
On Wed, Oct 4, 2017 at 12:09 PM Serge E. Hallyn  wrote:

> Hi,
>
> I've inherited a few vsphere machines where I was hoping to use juju
> to fire off openstack etc.  I've been trying to use the vsphere
> provider (which I was excited to see existed), but am seeing a few
> inconsistencies, so had a few questions.
>
> The first blunt question - is this going to be a maintained driver,
> or am I in 6 months likely to find the vsphere driver dropped?
>

We are actively working on making the vsphere provider to be a great
experience in the Juju 2.3 release. There's some more work to be done for
mirroring VMDKs from cloud-images, but otherwise I think everything's
working well now.

I don't have any reason to believe that we would drop the provider, or to
reduce focus on quality. People seem to want it :)

The second is motivating the first - when I looked at
> https://jujucharms.com/docs/2.1/help-vmware it says hardware version
> 8 (ESX 5.0) should be sufficient.  But in fact juju has a ubuntu.ovf
> hardcoded in it that specifies 'vmx-10', which is ESX 5.5..  I currently
> have 5 ESX 5.1 machines and one 6.0.
>

To my knowledge, Juju has only been tested with ESXi 5.5 and 6.0. In terms
of hardware support, version 8 seems like it should be sufficient. I'm not
sure about the APIs we're using, but we don't use a lot, so it wouldn't
surprise me if ESXi 5.1 just works.

If you're able to tweak the OVF and build Juju from source, that would be a
great help. Otherwise I will check what we require in terms of APIs when I
return from vacation next week - and try it out and report back. If it
works, then we can look to update the OVF for Juju 2.3.

Even with a custom DC using only the 6.0 host, I have some (probably
> proxy) issues bootstrapping, which I'm sure are surmountable - but the
> answer to Q1 will decide whether it's worth pursuing that further, or
> whether I should spend my time elsewhere :)
>

Please file a bug if you're still having issues. Juju 2.3 beta 1 is
imminent, so please use that if you can.

Cheers,
Andrew

thanks,
> -serge
>
> --
> 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: vsphere support

2017-10-04 Thread Serge E. Hallyn
Quoting Dmitrii Shcherbakov (dmitrii.shcherba...@canonical.com):
> Hi Serge,
> 
> >From my perspective Juju will continue getting more support for vSphere
> provider as VMware is used by some customers that do not want to go with a
> full-blown bare-metal deployment and just have spare VMs.

Ok, that's encouraging.

> I personally had to do a deployment of K8s on ESX (don't remember which
> version they had) but I had to use the manual provider because a custom
> provisioning method and IPAM was used on-site without DHCP so there was no
> way to use the proper vSphere provider.

I've got a DNS server, but it's separate from the juju server right now.
Hopefully that is ok.

> >From the commercial perspective VMware is listed in a (fresh) datasheet
> below and we do have that demand.
> 
> https://assets.ubuntu.com/v1/b35eca50-Enterprise-Kubernetes-datasheet.pdf?_ga=2.138877683.1310562253.1507133746-467575700.1507133746
> 
> Best Regards,
> Dmitrii Shcherbakov
> 
> Field Software Engineer
> IRC (freenode): Dmitrii-Sh

Thanks,
-serge

-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju


Re: vsphere support

2017-10-04 Thread christian . setzer

 Hi

I have a openstack charm installation and kubernetes cluster running  
currently.
I  remember trying vsphere support as well but it didnt work. sorry  
but that just came to my mind. so i was bound to use maas in order to  
use vsphere and juju.


BR

  

 Christian

Quoting "Serge E. Hallyn" <se...@hallyn.com>:

Well if using MAAS would be easier, I'm happy to do that.  I  
actually just hadn't

considered it a possibility, but I see at
https://askubuntu.com/questions/870624/configuring-maas-with-vmware-esxi-nodes-and-virsh
that it may be :)

I wonder what would be the difference in range of charms that I can  
actually use

if I use MAAS vs directly use juju vsphere support.

-serge

Quoting christian.set...@freies-franken.org  
(christian.set...@freies-franken.org):

Hi

Thats typical me. I implied that you use maas and have trouble
setting it up with juju as a cloud. Pardon me. Thats how i work ;-)

BR

 

Christian

Quoting "Serge E. Hallyn" <se...@hallyn.com>:

Quoting christian.set...@freies-franken.org
(christian.set...@freies-franken.org):
Hi

6.0 should work. It does for me and even 6.5.

Ok - like I say I only have the one 6.0 so not ideal, but a starting
point.

I already have offered the devs that they can use my environment to
sort out all the open bugs. But so far nobody was willing to do so.

...

What i did maybe helpful do you...

#!/bin/bash
maas - machines add-chassis chassis_type='vmware'
username='\' password=''
protocol='https+unverified' hostname=
prefix_filter= domain=

Pardon my ignorance - but I don't know what I'm looking at :)  Do
you run that on the juju server then target juju at that maas
instance?

Without the https+unverified i couldnt get it to work adding a
chassis because in the GUI the protocol field is missing.

BR

Christian

thanks,-serge


pub  2048R/DF0339A2 2017-09-10 Christian Setzer  
<christian.set...@freies-franken.org>

sub  2048R/68E412B2 2017-09-10


--
Juju mailing list
Juju@lists.ubuntu.comModify settings or unsubscribe at:  
https://lists.ubuntu.com/mailman/listinfo/juju


binOPBg1iQWxH.bin
Description: PGP Public Key
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju


Re: vsphere support

2017-10-04 Thread Marco Ceppi
There really shouldn't be any difference in the charms that are deploy-able
on MAAS vs vSphere. The Juju team has made a lot of strides in 2.2 and the
upcoming 2.3 release to support vSphere directly. MAAS management of
vSphere is slightly different than Juju if I recall correctly, but
shouldn't impact charm compatibility.

Marco

On Wed, Oct 4, 2017 at 1:28 PM Serge E. Hallyn <se...@hallyn.com> wrote:

> Well if using MAAS would be easier, I'm happy to do that.  I actually just
> hadn't
> considered it a possibility, but I see at
>
> https://askubuntu.com/questions/870624/configuring-maas-with-vmware-esxi-nodes-and-virsh
> that it may be :)
>
> I wonder what would be the difference in range of charms that I can
> actually use
> if I use MAAS vs directly use juju vsphere support.
>
> -serge
>
> Quoting christian.set...@freies-franken.org (
> christian.set...@freies-franken.org):
> >  Hi
> >
> > Thats typical me. I implied that you use maas and have trouble
> > setting it up with juju as a cloud. Pardon me. Thats how i work ;-)
> >
> > BR
> >
> >
> >
> >  Christian
> >
> > Quoting "Serge E. Hallyn" <se...@hallyn.com>:
> >
> > >Quoting christian.set...@freies-franken.org
> > >(christian.set...@freies-franken.org):
> > >>Hi
> > >>
> > >>6.0 should work. It does for me and even 6.5.
> > >
> > >Ok - like I say I only have the one 6.0 so not ideal, but a starting
> > >point.
> > >
> > >>I already have offered the devs that they can use my environment to
> > >>sort out all the open bugs. But so far nobody was willing to do so.
> > >
> > >...
> > >
> > >>What i did maybe helpful do you...
> > >>
> > >>#!/bin/bash
> > >>maas - machines add-chassis chassis_type='vmware'
> > >>username='\' password=''
> > >>protocol='https+unverified' hostname=
> > >>prefix_filter= domain=
> > >
> > >Pardon my ignorance - but I don't know what I'm looking at :)  Do
> > >you run that on the juju server then target juju at that maas
> > >instance?
> > >
> > >>Without the https+unverified i couldnt get it to work adding a
> > >>chassis because in the GUI the protocol field is missing.
> > >>
> > >>BR
> > >>
> > >>Christian
> > >
> > >thanks,-serge
>
> > pub  2048R/DF0339A2 2017-09-10 Christian Setzer <
> christian.set...@freies-franken.org>
> > sub  2048R/68E412B2 2017-09-10
>
>
> --
> 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: vsphere support

2017-10-04 Thread Serge E. Hallyn
Well if using MAAS would be easier, I'm happy to do that.  I actually just 
hadn't
considered it a possibility, but I see at
https://askubuntu.com/questions/870624/configuring-maas-with-vmware-esxi-nodes-and-virsh
that it may be :)

I wonder what would be the difference in range of charms that I can actually use
if I use MAAS vs directly use juju vsphere support.

-serge

Quoting christian.set...@freies-franken.org 
(christian.set...@freies-franken.org):
>  Hi
> 
> Thats typical me. I implied that you use maas and have trouble
> setting it up with juju as a cloud. Pardon me. Thats how i work ;-)
> 
> BR
> 
>   
> 
>  Christian
> 
> Quoting "Serge E. Hallyn" <se...@hallyn.com>:
> 
> >Quoting christian.set...@freies-franken.org
> >(christian.set...@freies-franken.org):
> >>Hi
> >>
> >>6.0 should work. It does for me and even 6.5.
> >
> >Ok - like I say I only have the one 6.0 so not ideal, but a starting
> >point.
> >
> >>I already have offered the devs that they can use my environment to
> >>sort out all the open bugs. But so far nobody was willing to do so.
> >
> >...
> >
> >>What i did maybe helpful do you...
> >>
> >>#!/bin/bash
> >>maas - machines add-chassis chassis_type='vmware'
> >>username='\' password=''
> >>protocol='https+unverified' hostname=
> >>prefix_filter= domain=
> >
> >Pardon my ignorance - but I don't know what I'm looking at :)  Do
> >you run that on the juju server then target juju at that maas
> >instance?
> >
> >>Without the https+unverified i couldnt get it to work adding a
> >>chassis because in the GUI the protocol field is missing.
> >>
> >>BR
> >>
> >>Christian
> >
> >thanks,-serge

> pub  2048R/DF0339A2 2017-09-10 Christian Setzer 
> <christian.set...@freies-franken.org>
> sub  2048R/68E412B2 2017-09-10


-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju


Re: vsphere support

2017-10-04 Thread christian . setzer

 Hi

Thats typical me. I implied that you use maas and have trouble setting  
it up with juju as a cloud. Pardon me. Thats how i work ;-)


BR

  

 Christian

Quoting "Serge E. Hallyn" :

Quoting christian.set...@freies-franken.org  
(christian.set...@freies-franken.org):

Hi

6.0 should work. It does for me and even 6.5.


Ok - like I say I only have the one 6.0 so not ideal, but a starting
point.


I already have offered the devs that they can use my environment to
sort out all the open bugs. But so far nobody was willing to do so.


...


What i did maybe helpful do you...

#!/bin/bash
maas - machines add-chassis chassis_type='vmware'
username='\' password=''
protocol='https+unverified' hostname=
prefix_filter= domain=


Pardon my ignorance - but I don't know what I'm looking at :)  Do
you run that on the juju server then target juju at that maas
instance?


Without the https+unverified i couldnt get it to work adding a
chassis because in the GUI the protocol field is missing.

BR

Christian


thanks,-serge


bins1Cqe7aYAn.bin
Description: PGP Public Key
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju


Re: vsphere support

2017-10-04 Thread Serge E. Hallyn
Quoting christian.set...@freies-franken.org 
(christian.set...@freies-franken.org):
>  Hi
> 
> 6.0 should work. It does for me and even 6.5.

Ok - like I say I only have the one 6.0 so not ideal, but a starting
point.

> I already have offered the devs that they can use my environment to
> sort out all the open bugs. But so far nobody was willing to do so.

...

> What i did maybe helpful do you...
> 
> #!/bin/bash
>  maas - machines add-chassis chassis_type='vmware'
> username='\' password=''
> protocol='https+unverified' hostname=
> prefix_filter= domain=

Pardon my ignorance - but I don't know what I'm looking at :)  Do
you run that on the juju server then target juju at that maas
instance?

> Without the https+unverified i couldnt get it to work adding a
> chassis because in the GUI the protocol field is missing.
> 
> BR
> 
> Christian

thanks,
-serge

-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju


Re: vsphere support

2017-10-04 Thread Dmitrii Shcherbakov
Hi Serge,

>From my perspective Juju will continue getting more support for vSphere
provider as VMware is used by some customers that do not want to go with a
full-blown bare-metal deployment and just have spare VMs.

I personally had to do a deployment of K8s on ESX (don't remember which
version they had) but I had to use the manual provider because a custom
provisioning method and IPAM was used on-site without DHCP so there was no
way to use the proper vSphere provider.

>From the commercial perspective VMware is listed in a (fresh) datasheet
below and we do have that demand.

https://assets.ubuntu.com/v1/b35eca50-Enterprise-Kubernetes-datasheet.pdf?_ga=2.138877683.1310562253.1507133746-467575700.1507133746

Best Regards,
Dmitrii Shcherbakov

Field Software Engineer
IRC (freenode): Dmitrii-Sh

On Wed, Oct 4, 2017 at 12:08 PM, Serge E. Hallyn  wrote:

> Hi,
>
> I've inherited a few vsphere machines where I was hoping to use juju
> to fire off openstack etc.  I've been trying to use the vsphere
> provider (which I was excited to see existed), but am seeing a few
> inconsistencies, so had a few questions.
>
> The first blunt question - is this going to be a maintained driver,
> or am I in 6 months likely to find the vsphere driver dropped?
>
> The second is motivating the first - when I looked at
> https://jujucharms.com/docs/2.1/help-vmware it says hardware version
> 8 (ESX 5.0) should be sufficient.  But in fact juju has a ubuntu.ovf
> hardcoded in it that specifies 'vmx-10', which is ESX 5.5..  I currently
> have 5 ESX 5.1 machines and one 6.0.
>
> Even with a custom DC using only the 6.0 host, I have some (probably
> proxy) issues bootstrapping, which I'm sure are surmountable - but the
> answer to Q1 will decide whether it's worth pursuing that further, or
> whether I should spend my time elsewhere :)
>
> thanks,
> -serge
>
> --
> 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: vsphere support

2017-10-04 Thread christian . setzer

 Hi

6.0 should work. It does for me and even 6.5.

I already have offered the devs that they can use my environment to  
sort out all the open bugs. But so far nobody was willing to do so.


What i did maybe helpful do you...

#!/bin/bash
 maas - machines add-chassis chassis_type='vmware'  
username='\' password=''  
protocol='https+unverified' hostname=  
prefix_filter= domain=


Without the https+unverified i couldnt get it to work adding a chassis  
because in the GUI the protocol field is missing.


BR

Christian
  


Quoting "Serge E. Hallyn" :


Hi,

I've inherited a few vsphere machines where I was hoping to use juju
to fire off openstack etc.  I've been trying to use the vsphere
provider (which I was excited to see existed), but am seeing a few
inconsistencies, so had a few questions.

The first blunt question - is this going to be a maintained driver,
or am I in 6 months likely to find the vsphere driver dropped?

The second is motivating the first - when I looked at
https://jujucharms.com/docs/2.1/help-vmware it says hardware version
8 (ESX 5.0) should be sufficient.  But in fact juju has a ubuntu.ovf
hardcoded in it that specifies 'vmx-10', which is ESX 5.5..  I currently
have 5 ESX 5.1 machines and one 6.0.

Even with a custom DC using only the 6.0 host, I have some (probably
proxy) issues bootstrapping, which I'm sure are surmountable - but the
answer to Q1 will decide whether it's worth pursuing that further, or
whether I should spend my time elsewhere :)

thanks,
-serge

--
Juju mailing list
Juju@lists.ubuntu.comModify settings or unsubscribe at:  
https://lists.ubuntu.com/mailman/listinfo/juju


binoDYal2_104.bin
Description: PGP Public Key
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju


vsphere support

2017-10-04 Thread Serge E. Hallyn
Hi,

I've inherited a few vsphere machines where I was hoping to use juju
to fire off openstack etc.  I've been trying to use the vsphere
provider (which I was excited to see existed), but am seeing a few
inconsistencies, so had a few questions.

The first blunt question - is this going to be a maintained driver,
or am I in 6 months likely to find the vsphere driver dropped?

The second is motivating the first - when I looked at
https://jujucharms.com/docs/2.1/help-vmware it says hardware version
8 (ESX 5.0) should be sufficient.  But in fact juju has a ubuntu.ovf
hardcoded in it that specifies 'vmx-10', which is ESX 5.5..  I currently
have 5 ESX 5.1 machines and one 6.0.

Even with a custom DC using only the 6.0 host, I have some (probably
proxy) issues bootstrapping, which I'm sure are surmountable - but the
answer to Q1 will decide whether it's worth pursuing that further, or
whether I should spend my time elsewhere :)

thanks,
-serge

-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju