Re: [Openstack-operators] Upgrade OpenStack Juno to Mitaka

[Michael Stang]

I think we give it a try then, thank you :-)
 
Kind regards,
Michael

> Simon Leinen  hat am 18. Juni 2016 um 16:21
> geschrieben:
>
>
> Michael Stang writes:
> > Is this one the actual guid for upgrades, and is it valid for every
> > upgrade or ony for specific versions?:
> > http://docs.openstack.org/ops-guide/ops_upgrades.html
>
> Yes, that's part of the official Operations Guide. It is not
> version-specific. The examples are based on Ubuntu as the underlying OS
> distribution. But the approach and recommendations are general.
> --
> Simon.
 ___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] Ops Meetups Team - Meeting Tuesday 1400 UTC (mid-cycle venue selection!)

[Tom Fifield]

Hi all,

We're having a special meeting:

Tuesday, 21 of Jun at 1400 UTC [1]

where we will decide the venue for the next mid-cycle will be!

See you in IRC[2], in the #openstack-operators channel.


Details about the group, and the link to the agenda etherpad, can be 
found at:


https://wiki.openstack.org/wiki/Ops_Meetups_Team#Meeting_Information



Regards,


Tom


[1] To see this in your local time - check: 
http://www.timeanddate.com/worldclock/fixedtime.html?msg=Ops+Meetups+Team=20160621T14


[2] If you're new to IRC, there's a great guide here: 
http://docs.openstack.org/upstream-training/irc.html


___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] [Magnum] Container on bare metal or container on VM

[Hieu LE]

Hi Hongbin Lu,

Thanks for your reply. I have responded inline.

BRs,
Hieu LE.

> On Sun, Jun 19, 2016 at 10:58 PM, Hongbin Lu  wrote:
> >
> >> 1. What is the pros/cons of deployment containers on VMs comparing with
> >> containers on bare metal? I have seen RackSpace providing their
> >> container service on bare metal and some other providers, but Amazon
> >> use container on VM instead.
> >> The only problem I saw with container on VM is only about management of
> >> quota and resources. Deploying containers on VM will lead us to think
> >> about whether we need to provide more containers on x VM for user or we
> >> need to provide x+1 VMs for user to scale based on their needs. There
> >> are 2 layers for operators to manage: 1st is VMs quota/resources and
> >> 2nd is containers.
> > [Hongbin Lu] Agree with you that containers on VMs are more complex to 
> > manage. There are other cons as well. For example, networking and storage 
> > are harder to setup. It is slower to scale up (because the speed to spin up 
> > VMs is not as fast as spinning up containers). In comparison, there are 
> > several pros. First, running containers on VMs provide strong isolation 
> > between containers of different tenants. Second, it can reuse the same 
> > resource pool to run VMs and containers (instead of creating a dedicated 
> > resource pool for running containers).

Yeah, multi-tenancy is the good point of containers on VM but the
second pros can lead to complex managements.

> >
> >> 2. Currently Magnum is on her way to implement the integration with
> >> Ironic but I can not see the clearer way to keep track about this
> >> feature (I have read the etherpad of Magnum team after summit). My team
> >> really want to contribute in this feature but we need something clearer
> >> to make a decision. Can you provide us some specs or related bp?
> > [Hongbin Lu] Here is the BP: 
> > https://blueprints.launchpad.net/magnum/+spec/magnum-baremetal-full-support 
> > . Currently, we have the Heat templates to provision k8s on top of Ironic 
> > instances. The next step is to introduce an ironic bay to deliver the full 
> > support. Spyros (the BP owner) will report the latest status every weeks in 
> > the Magnum team meeting, so you can keep track of the status there. I 
> > encourage you to contact Spyros if you want to contribute in this feature. 
> > I believe Spyros will coordinate the efforts.

Thank you, we will start investigating at this BP.

>
>>
>> Thanks,
>> Hieu LE.
>>
>> --
>> -BEGIN GEEK CODE BLOCK-
>> Version: 3.1
>> GCS/CM/IT/M/MU d-@? s+(++):+(++) !a C()$ ULC(++)$ P
>> L++(+++)$ E !W N* o+ K w O- M V- PS+ PE++ Y+ PGP+ t 5 X R tv+
>> b+(++)>+++ DI- D+ G e++(+++) h-- r(++)>+++ y-
>> --END GEEK CODE BLOCK--



-- 
-BEGIN GEEK CODE BLOCK-
Version: 3.1
GCS/CM/IT/M/MU d-@? s+(++):+(++) !a C()$ ULC(++)$ P
L++(+++)$ E !W N* o+ K w O- M V- PS+ PE++ Y+ PGP+ t 5 X R tv+
b+(++)>+++ DI- D+ G e++(+++) h-- r(++)>+++ y-
--END GEEK CODE BLOCK--

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] [Magnum] Container on bare metal or container on VM

[Hongbin Lu]

Hi Hieu,

I replied inline.

Best regards,
Hongbin

> -Original Message-
> From: Hieu LE [mailto:hieul...@gmail.com]
> Sent: June-19-16 9:17 AM
> To: openstack-operators@lists.openstack.org
> Cc: Hongbin Lu
> Subject: [Magnum] Container on bare metal or container on VM
> 
> Hi folks,
> CC Hongbin Lu - PTL of Magnum and Zun.
> 
> (sorry for cross-posting because of sending to wrong ML)
> 
> I am very interested in container-related projects in OpenStack
> ecosystems, especially Magnum and Kolla and I also have a plan to
> deploy Magnum in my lab for HPC researching purposes. But I have some
> questions regarding of deployment model of Magnum:
> 1. What is the pros/cons of deployment containers on VMs comparing with
> containers on bare metal? I have seen RackSpace providing their
> container service on bare metal and some other providers, but Amazon
> use container on VM instead.
> The only problem I saw with container on VM is only about management of
> quota and resources. Deploying containers on VM will lead us to think
> about whether we need to provide more containers on x VM for user or we
> need to provide x+1 VMs for user to scale based on their needs. There
> are 2 layers for operators to manage: 1st is VMs quota/resources and
> 2nd is containers.
[Hongbin Lu] Agree with you that containers on VMs are more complex to manage. 
There are other cons as well. For example, networking and storage are harder to 
setup. It is slower to scale up (because the speed to spin up VMs is not as 
fast as spinning up containers). In comparison, there are several pros. First, 
running containers on VMs provide strong isolation between containers of 
different tenants. Second, it can reuse the same resource pool to run VMs and 
containers (instead of creating a dedicated resource pool for running 
containers).

> 2. Currently Magnum is on her way to implement the integration with
> Ironic but I can not see the clearer way to keep track about this
> feature (I have read the etherpad of Magnum team after summit). My team
> really want to contribute in this feature but we need something clearer
> to make a decision. Can you provide us some specs or related bp?
[Hongbin Lu] Here is the BP: 
https://blueprints.launchpad.net/magnum/+spec/magnum-baremetal-full-support . 
Currently, we have the Heat templates to provision k8s on top of Ironic 
instances. The next step is to introduce an ironic bay to deliver the full 
support. Spyros (the BP owner) will report the latest status every weeks in the 
Magnum team meeting, so you can keep track of the status there. I encourage you 
to contact Spyros if you want to contribute in this feature. I believe Spyros 
will coordinate the efforts.

> 
> Thanks,
> Hieu LE.
> 
> --
> -BEGIN GEEK CODE BLOCK-
> Version: 3.1
> GCS/CM/IT/M/MU d-@? s+(++):+(++) !a C()$ ULC(++)$ P
> L++(+++)$ E !W N* o+ K w O- M V- PS+ PE++ Y+ PGP+ t 5 X R tv+
> b+(++)>+++ DI- D+ G e++(+++) h-- r(++)>+++ y-
> --END GEEK CODE BLOCK--
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] [Magnum] Container on bare metal or container on VM

[Hieu LE]

Hi folks,
CC Hongbin Lu - PTL of Magnum and Zun.

(sorry for cross-posting because of sending to wrong ML)

I am very interested in container-related projects in OpenStack
ecosystems, especially Magnum and Kolla and I also have a plan to
deploy Magnum in my lab for HPC researching purposes. But I have some
questions regarding of deployment model of Magnum:
1. What is the pros/cons of deployment containers on VMs comparing
with containers on bare metal? I have seen RackSpace providing their
container service on bare metal and some other providers, but Amazon
use container on VM instead.
The only problem I saw with container on VM is only about management
of quota and resources. Deploying containers on VM will lead us to
think about whether we need to provide more containers on x VM for
user or we need to provide x+1 VMs for user to scale based on their
needs. There are 2 layers for operators to manage: 1st is VMs
quota/resources and 2nd is containers.
2. Currently Magnum is on her way to implement the integration with
Ironic but I can not see the clearer way to keep track about this
feature (I have read the etherpad of Magnum team after summit). My
team really want to contribute in this feature but we need something
clearer to make a decision. Can you provide us some specs or related
bp?

Thanks,
Hieu LE.

-- 
-BEGIN GEEK CODE BLOCK-
Version: 3.1
GCS/CM/IT/M/MU d-@? s+(++):+(++) !a C()$ ULC(++)$ P
L++(+++)$ E !W N* o+ K w O- M V- PS+ PE++ Y+ PGP+ t 5 X R tv+
b+(++)>+++ DI- D+ G e++(+++) h-- r(++)>+++ y-
--END GEEK CODE BLOCK--

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators