Magnum queens, uses kubernetes 1.9.3 by default.
You can upgrade to v1.10.11-1. From a quick test
v1.11.5-1 is also compatible with 1.9.x.
We are working to make this painless, sorry you
have to ssh to the nodes for now.
Cheers,
Spyros
On Mon, 3 Dec 2018 at 23:24, Spyros Trigazis wrote
Hello all,
Following the vulnerability [0], with magnum rocky and the kubernetes driver
on fedora atomic you can use this tag "v1.11.5-1" [1] for new clusters. To
upgrade
the apiserver in existing clusters, on the master node(s) you can run:
sudo atomic pull --storage ostree
Hello team,
This is a reminder for the upcoming magnum meeting [0].
For convenience you can import this from here [1] or view it in html here
[2].
Cheers,
Spyros
[0]
https://wiki.openstack.org/wiki/Meetings/Containers#Weekly_Magnum_Team_Meeting
[1]
It is constraints only. There is no project
that requires the new version.
Spyros
On Mon, 6 Aug 2018, 19:36 Matthew Thode, wrote:
> On 18-08-06 18:34:42, Spyros Trigazis wrote:
> > Hello,
> >
> > I have requested a release for python-magnumclient [0].
> > Per Doug H
Hello,
I have requested a release for python-magnumclient [0].
Per Doug Hellmann's comment in [0], I am requesting a FFE for
python-magnumclient.
Apologies for the inconvenience,
Spyros
[0] https://review.openstack.org/#/c/589138/
On Fri, 3 Aug 2018 at 18:52, Sean McGinnis wrote:
> Today
Hello OpenStack community!
I would like to nominate myself as PTL for the Magnum project for the
Stein cycle.
In the last cycle magnum became more stable and is reaching the point
of becoming a feature complete solution for providing managed container
clusters for private or public OpenStack
, but if we put both of them into single one config script.
> The script could be very complex. That's why I think we should define some
> naming and logging rules/policies for those scripts for long term
> maintenance to make our life easier. Thoughts?
>
> On 25/06/18 19:20, Spyros T
Hello list,
I'm excited to nominate Feilong as Core Reviewer for the Magnum project.
Feilong has contributed many features like Calico as an alternative CNI for
kubernetes, make coredns scale proportionally to the cluster, improved
admin operations on clusters and improved multi-master
meetings, Tuesday 1000UTC and Thursday
1700UTC.
You can always consult this page [1] for future meetings.
Cheers,
Spyros
[1] https://wiki.openstack.org/wiki/Meetings/Containers
On Wed, 20 Jun 2018 at 18:05, Spyros Trigazis wrote:
> Hello list,
>
> We are going to have a second weekl
Hello list,
We are going to have a second weekly meeting for magnum for 3 weeks
as a test to reach out to contributors in the Americas.
You can join us tomorrow (or today for some?) at 1700UTC in
#openstack-containers .
Cheers,
Spyros
2
Cheers,
Spyros
ps We will update the magnum docs as well
[1]
http://git.openstack.org/cgit/openstack/heat/tree/heat/engine/service.py#n375
On Mon, 18 Jun 2018 at 19:39, Jay Pipes wrote:
> +openstack-dev since I believe this is an issue with the Heat source code.
>
> On 06/18/20
Hi Sergey,
In magnum queens we can set the private ca as a service account key.
Here [1] we can set the ca.key file. When the label cert_manager_api is
set to true.
Cheers,
Spyros
[1]
Hello,
After discussion with the keystone team at the above session, keystone
will not provide a way to transfer trusts nor application credentials,
since it doesn't address the above problem (the member that leaves the team
can auth with keystone if he has the trust/app-creds).
In magnum we
Hello,
Heads up, the containers team meeting has changed from 1600UTC to 1000UTC.
See you there tomorrow at #openstack-meeting-alt !
Spyros
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
the project up to date
and increase the user base.
For the next cycle, I want to enable the Magnum team to complete the
work on cluster upgrades, cluster federation, cluster auto-healing,
support for different container runtimes and container network backends.
Thanks for considering me,
Spyros
Hi Greg,
You can try to build an image with this process [1]. I haven't used for
some time since
we rely on the upstream image.
Another option that I would like to investigate is to build a system
container with
frakti or clear container similar to these container images [2] [3] [4].
Then you
er any bugs please report them and if you need anything free
to ask here or in #openstack-containers.
Cheers,
Spyros
>
>
> El mié., 22 nov. 2017 a las 5:30, Spyros Trigazis (<strig...@gmail.com>)
> escribió:
>>
>> Hi Sergio,
>>
>> On 22 November 2017 at 0
I forgot to include the Pike release notes
https://docs.openstack.org/releasenotes/magnum/pike.html
Spyros
On 22 November 2017 at 09:29, Spyros Trigazis <strig...@gmail.com> wrote:
> Hi Sergio,
>
> On 22 November 2017 at 03:31, Sergio Morales Acuña <sem...@gmail.com>
Hi Sergio,
On 22 November 2017 at 03:31, Sergio Morales Acuña wrote:
> I'm using Openstack Ocata and trying Magnum.
>
> I encountered a lot of problems but I been able to solved many of them.
Which problems did you encounter? Can you be more specific? Can we solve them
for
Hi Vahric,
A very important reason that we use fedora atomic is that we
are no maintaining our special image. We use the upstream
operating system and we rely on the Fedora Project and we
contribute back to it. If we use ubuntu we would need to
maintain our special qcow image.
We also use the
Magnum - Spyros Trigazis - <strig...@gmail.com>
Thanks!
On 9 October 2017 at 23:24, Kendall Nelson <kennelso...@gmail.com> wrote:
> Wanted to keep this thread towards the top of inboxes for those I haven't
> heard from yet.
>
> About a 1/4 of the way booked, so there a
Hi Greg,
Can you revisit your policy configuration and try again?
See here:
http://git.openstack.org/cgit/openstack/magnum/plain/etc/magnum/policy.json?h=stable/newton
Cheers,
Spyros
On 22 September 2017 at 13:49, Waines, Greg wrote:
> Just another note on this ...
/meetings/containers/2017/containers.2017-08-22-16.00.html
[1] https://review.openstack.org/#/c/489609/
On 22 August 2017 at 17:47, Spyros Trigazis <strig...@gmail.com> wrote:
> Hello,
>
> Recently we decided to have bi-weekly meetings. Starting from today we will
> have weekly meetin
Hello,
Recently we decided to have bi-weekly meetings. Starting from today we will
have weekly meetings again.
From now on, we will have our meeting every Tuesday at 1600 UTC
in #openstack-meeting-alt . For today, that is in 13 minutes.
Cheers,
Spyros
.
Thanks for considering me,
Spyros Trigazis
[0] https://review.openstack.org/490893
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http
Thanks for the reminder.
python-magnumclient https://review.openstack.org/#/c/472718/
Cheers,
Spyros
On 9 June 2017 at 16:39, Doug Hellmann wrote:
> We have several teams with library deliverables that haven't seen
> any releases at all yet this cycle. Please review the
t can
> adopt Kuryr/Fuxi which will give you a better OpenStack integration.
>
>
>
> Best regards,
>
> Hongbin
>
fuxi feature request: Add authentication using a trustee and a trustID.
Cheers,
Spyros
>
>
> *From:* Spyros Trigazis [mailto:strig...@gmail.com]
&g
FYI, there is already a cinder volume driver for docker available, written
in golang, from rexray [1].
Our team recently contributed to libstorage [3], it could support manila
too. Rexray
also supports the popular cloud providers.
Magnum's docker swarm cluster driver, already leverages rexray
On 17 May 2017 at 13:58, Spyros Trigazis <strig...@gmail.com> wrote:
>
>
> On 17 May 2017 at 06:25, KiYoun Sung <kys...@devstack.co.kr> wrote:
>
>> Hello,
>> Magnum team.
>>
>> I Installed Openstack newton and magnum.
>> I installed Magnu
On 17 May 2017 at 06:25, KiYoun Sung wrote:
> Hello,
> Magnum team.
>
> I Installed Openstack newton and magnum.
> I installed Magnum by source(master branch).
>
> I have two questions.
>
> 1.
> After installation,
> I created kubernetes cluster and it's CREATE_COMPLETE,
>
IMO, coe is a little confusing. It is a term used by people related somehow
to the magnum community. When I describe to users how to use magnum,
I spent a few moments explaining what we call coe.
I prefer one of the following:
* openstack magnum cluster create|delete|...
* openstack mcluster
Hi,
You haven't installed the magnum client. The service is running
but you don't have the client.
You need the client installed and to create and source the RC file.
Spyros
On 9 March 2017 at 07:49, Yu Wei wrote:
> Hi guys,
>
> After installing openstack ocata magnum,
at 17:01 +0100, Spyros Trigazis wrote:
> > Hi.
> >
> > I have done it by checking the ip address of the master. The current
> > state of
> > the heat drivers doesn't allow the distinction between master > 1 or
> > master=1.
> >
>
> Please, could
Hi.
I have done it by checking the ip address of the master. The current state
of
the heat drivers doesn't allow the distinction between master > 1 or
master=1.
Spyros
On 31 January 2017 at 16:33, Kevin Lefevre wrote:
> Hi, Docker 1.13 has been released with several
ment but it saves your overhead to deprecate the old version and roll
> out the new version.
>
>
>
> Best regards,
>
> Hongbin
>
>
>
> *From:* Spyros Trigazis [mailto:strig...@gmail.com]
> *Sent:* January-24-17 3:47 PM
> *To:* OpenStack Development Mailing L
Hi.
IMO, you should add a BP and start by adding a v2 driver in /contrib.
Cheers,
Spyros
On Jan 24, 2017 20:44, "Kevin Lefevre" wrote:
> Hi,
>
> The CoreOS template is not really up to date and in sync with upstream
> CoreOS « Best Practice »
I think for magnum we are OK.
This job [1] finished using keystone v3 [2]
Spyros
[1]
http://logs.openstack.org/93/400593/9/check/gate-functional-dsvm-magnum-api/93e8c14/
[2]
Hi all,
In magnum, we implement cluster drivers for the different combinations
of COEs (Container Orchestration Engines) and Operating Systems. The
reasoning behind it is to better encapsulate driver-specific logic and to
allow
operators deploy custom drivers with their deployment specific
+1 for both
Cheers,
Spyros
On 8 November 2016 at 03:34, Yuanying OTSUKA wrote:
> +1 for both.
>
> Best regards
> -yuanying
>
> 2016年11月8日(火) 4:23 Hongbin Lu :
>
>> +1!
>>
>> Both jvgrant and yatin contributed a lot to the Magnum project. It would
lated with your topic.
> So thank you for the providing all items here.
> Rabi, can we add link on this mail to etherpad ? (it will save our time
> during session :) )
>
> On 10 October 2016 at 18:11, Spyros Trigazis <strig...@gmail.com> wrote:
>
>> Hi heat and ma
Hi heat and magnum.
Apart from the scalability issues that have been observed, I'd like to
add few more subjects to discuss during the summit.
1. One nested stack per node and linear scale of cluster creation
time.
1.1
For large stacks, the creation of all nested stack scales linearly. We
Hi Kamal.
On 3 October 2016 at 09:33, kamalakannan sanjeevan <
chirukamalakan...@gmail.com> wrote:
> Hi All,
>
> I have installed Mitaka on ubuntu14.04. I have tried an all in one
> installation along with cinder using dd and then creating the
> cinder-volumes at /dev/loop2. The network neutron
Hi.
count me in, Samsung Galaxy A3 Android 5.0.2.
Cheers,
Spyros
On 3 September 2016 at 11:31, Fawaz Mohammed
wrote:
> Interested, Android version 6.0.1
>
> On Sep 3, 2016 9:09 AM, "Swapnil Kulkarni" wrote:
>
>> Count me in for Android beta
count is not registered to Steve,
> so we will just use the new account "openstackmagnum".
> Ton,
>
> [image: Inactive hide details for Spyros Trigazis ---08/02/2016 09:27:38
> AM---I just filed a ticket to acquire the username openstackma]Spyros
> Trigazis ---08/02/20
Hi,
better follow the quickstart guide [1].
Cheers,
Spyros
[1] http://docs.openstack.org/developer/magnum/dev/quickstart.html
On 5 August 2016 at 06:22, Yasemin DEMİRAL (BİLGEM BTE) <
yasemin.demi...@tubitak.gov.tr> wrote:
>
> Hi
>
> I try to magnum on devstack, in the manual Configure
I just filed a ticket to acquire the username openstackmagnum.
I included Hongbin's contact information explaining that he's the project's
PTL.
Thanks Steve,
Spyros
On 2 August 2016 at 13:29, Steven Dake (stdake) wrote:
> Ton,
>
> I may or may not have set it up early in
Hi Greg,
lbaas *v1* is required for magnum mitaka.
Cheers,
Spyros
On 18 July 2016 at 16:16, Waines, Greg wrote:
> Thanks Madhuri,
>
>
>
> This blueprint is ‘Accepted for Newton’.
>
> So in ‘Mitaka’ and before, LBAAS is required for Magnum ?
>
>
>
> Greg.
>
>
>
>
Hi.
I'd like to propose to move the "launch-instance" section [1] in project
repos along with the install-guide. If we won't move it, we must find an
appropriate place for it.
Cheers,
Spyros
[1]
http://docs.openstack.org/mitaka/install-guide-ubuntu/launch-instance.html
+1 on the modular approach by Rodrigo Caballero
I'm writing magnum's guide and I'm working on the debian guide. Debian's
guide will have a couple of differences and I plan to move them in other
files or/and break the existing common config files.
IMO, one of the goals of the project specific
r baremetal?
> 2. How to solve Ironic instance_info problem?
>
I'll look into this in more detail.
>
> Currently I have no idea, maybe time will solve these?
>
>
> Thanks
> -yuanying
>
Thanks,
Spyros
>
> 2016年6月21日(火) 0:30 Spyros Trigazis <strig...@gmail.co
ks
> -yuanying
>
>
> 2016年5月25日(水) 22:00 Yuanying OTSUKA <yuany...@oeilvert.org>:
>
>> Hi, Spyros
>>
>> I fixed a conflicts and upload following patch.
>> * https://review.openstack.org/#/c/320968/
>>
>> But it isn’t tested yet, maybe it does
Hi Gary.
On 13 June 2016 at 09:06, Duan, Li-Gong (Gary, HPServers-Core-OE-PSC) <
li-gong.d...@hpe.com> wrote:
> Hi Tom/All,
>
> >6. Ironic Integration:
> https://etherpad.openstack.org/p/newton-magnum-ironic-integration
> >- Start the implementation immediately
> >- Prefer quick work-around for
Hi Wally.
You can follow these instructions [1] to install from source
code (use the stable/mitaka branch when you'll clone).
Although, this guide is under the developer url, it's built for
operators. Keep in mind that you need Neutron/LBaaS V1.
Additionally there is this [2] puppet module.
Hi Hongbin.
CERN's location: https://goo.gl/maps/DWbDVjnAvJJ2
Cheers,
Spyros
On 8 June 2016 at 16:01, Hongbin Lu wrote:
> Ricardo,
>
> Thanks for the offer. Would I know where is the exact location?
>
> Best regards,
> Hongbin
>
> > -Original Message-
> > From:
This work aims to be published to magnum's developer page:
http://docs.openstack.org/developer/magnum/
Cheers,
Spyros
On 1 June 2016 at 17:30, Andreas Jaeger <a...@suse.com> wrote:
> On 06/01/2016 05:21 PM, Spyros Trigazis wrote:
>
>> Hi everyone,
>>
>> Is the i
Hi everyone,
Is the idea of having an install-guide from source and possibly
virtualenvs still under consideration?
I'd like to share with you what we are currently doing along with
the install-guide based on the cookiecutter template.
I have created this change [1] in our project repo.
Hi.
I have added https://wiki.openstack.org/wiki/Neutron/LBaaS/HowToRun
Regards,
Spyros
On 1 June 2016 at 16:39, Hongbin Lu wrote:
> Hi lbaas team,
>
>
>
> I wonder if there is an operator-facing installation guide for
> neutron-lbaas. I asked that because Magnum is
Hi Yuanying,
please upload your workaround. I can test it and try to fix the conflicts.
Even if it conflicts we can have some iterations on it.
I'll upload later what worked for me on devstack.
Thanks,
Spyros
On 25 May 2016 at 05:13, Yuanying OTSUKA wrote:
> Hi,
projects as
OpenStack
first-class citizens in the install-guide. Finally, an operator who want's
to install
a Big Tent project, should be informed about the project's prerequisites as
early
as possible.
Cheers,
Spyros Trigazis
(Member of Magnum)
On 14 May 2016 at 00:08, Laura Clymer <laura.
Hi,
since I work on the install docs (btw, I'll push in our repo in the next
hour), I could do it.
Spyros
On 11 May 2016 at 00:35, Anthony Chow wrote:
> HongBin,
>
> What is the skill requirement or credential for this documentation liaison
> role? I am interested in
I made a first attempt to factor out the configuration of different
storage drivers in this change [1].
Spyros
[1] https://review.openstack.org/#/c/284720/
On 19 April 2016 at 05:45, Eli Qiao wrote:
> Sure that is the things I want to cleanup long time before.
> I
+1
I'm a new contributor, but Eli made already a
good impression on me.
Cheers,
Spyros
On 1 April 2016 at 10:51, Cammann, Tom wrote:
> +1
>
> From: Hongbin Lu
> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <
>
62 matches
Mail list logo