Meeting time: 2015.07.21Moderator: Kirill Zaitsev, core from MirantisConference Summary:1.murano client and Murano dashboard upgrade to yaql1.0.Slagun is responsible for Mistral coordination with the yaql1.0 upgrade issue, Mistral need to upgrade together.2.OpenStack each project with Olso interface person.
Project
Liaison
IRC Handle
Summary of the 2015.07.14 sessionModerator: Kirill Zaitsev, core from MirantisPeriodic nightly builds, and then published through the mailing list, eventually no conclusion by which Mailinglist released1.yaql1.0 BPAction:kzaitsev from Slagun yaql1.0 BP with client and dashboard tasks.
JS linting Jobs (KZAITSEV_MB, 17:32:05)
Https://github.com/openstack/murano/blob/master/
Meeting time : 2016.may.10 1:00~2:00Chairperson: Serg Melikyan, from MirantisMeeting Summary:1. Murano Contributors Rules
Six usage Rule: Use it if the really necessary (for example if existing code would now work in Py3 at all. If It is a matter of performance only prefer readability
Do not import functions. Only module Imports is accepted
Commit-names for Murano-apps
ceilometer or other monitoring tools suppor Ted by Murano if its instances is running. The application Publisher can then specify the billing rules used with those metrics, essentially defining how much usage A service would cost the user.[Note This proposal was meant to define a project that provides billing information, but because different organizatio NS has different needs, it doesn ' t define actual payment methods; Payment May is handled by a
Meeting time : 2015.september.8th 1:00~2:00Chairperson: Serg Melikyan, PTL from MirantisMeeting Summary:1. Future ofSTACKFORGE/YAQL.Action: The OpenStack community choose a date upon which to perform a mass migration of all stackforge/projects into openstack/.The date is either October or November 7 (both Saturdays),As least likely to interfere with the release or summit.The community create a wiki page for
Meeting time : 2015.september.22th 1:00~2:00Chairperson: Serg Melikyan, PTL from MirantisMeeting Summary:1.About PTL CandidacyPIC: Serg MelikyanDesc: Our PTL (program Technical leads) Miss deadline for sending he candidacy as PTL for the next cycle.So it's up to TC (Technical Committee) to assign PTL for Murano.But I think he's still the Murano PTL for the next cycle.becasue lots of people support him. Link: https://wiki.openstack.org/wiki/PTL_Electio
Meeting time : 2015.september.29th 1:00~2:00Chairperson: Serg Melikyan, PTL from MirantisMeeting Summary:1.RabbitMQ DriverDesc: Murano used Kombu because Oslo.messaging uses it.In the Liberty, Murano left one bugs about the RabbitMQ.The Murano Engine with RabbitMQ andMurano Agent with RabbitMQ need to add heartbeat option,That allows user-to-control heartbeats fo
Meeting time : 2015.august.4th 1:00~2:00Chairperson: Serg Melikyan, PTL from MirantisMeeting Summary:1.Migrating to YAQL 1.0 status.PIC: Stan lagunStatus: All commits is on review and not yet merged.New YAQL engine should is fully functional at the moment.Though we need to fix PEP8, it passes all unit tests. The YAQL RC2 is released as soon as all YAQL commits got merged and test.Action: Kirill Zaitsev would write an e-mail to encourage Murano te
Meeting time : 2015.october.13th 1:00~2:00Chairperson: Serg Melikyan, PTL from MirantisMeeting Summary:1.Murano Networking ' max_environments 'Desc: Murano increased the number of environments per tenant in Mitaka.That means maximum number of environments this use a single router per tenant.The ' max_environments ' setting of [networking] group in MuranoConfiguration file defines the maximum number of netwo
Meeting time : 2015.november.4th 1:00~2:00Chairperson: Serg Melikyan, PTL from MirantisMeeting Summary:1.Tagging LibertyPIC: Kirill Zaitsev Desc: Murano is still in Liberty 1.0.0 version.Kirill would try to tag stable Branch 1.0.1 in this week,And everything seems to being fine with it.2.Jenkins Gate ChangedDesc: The GATE-MURANO-DEVSTACK-DSVM is useless now for muranoclient patches verification, and would b
Meeting time : 2016.may.31 1:00~2:00Chairperson: Kirill Zaitsev, from MirantisMeeting Summary:1.Action Item ReviewUpdate the wiki to mention new CPLs.KZAITSEV_MB Ping stable Reviewers to review the Backports.2.Murano packages move into Murano-appsThe leave Murano-core team as part of the Murano-app-core.I believe that
Meeting time : 2016.august.09 1:00~2:00Chairperson: Kirill Zaitsev, from MirantisMeeting Summary:1.Open Discussion1) Basically the idea was to clean up murano-apps repo. Some apps is simple and has little value,Other than examples-those would is deleted or would go to Murano repo under examples directory.2) Some apps is important, but small enough for a separate repo-we ' ll leave them in
Meeting time : 2016.june.7 1:00~2:00Chairperson: Kirill Zaitsev, from MirantisMeeting Summary:1.Action Item ReviewUpdate the wiki to mention new CPLs.KZAITSEV_MB Ping stable Reviewers to review the Backports.2.Murano packages move into Murano-appsThe leave Murano-core team as part of the Murano-app-core.I believe that
Meeting time : 2015.august.11th 1:00~2:00Chairperson: Serg Melikyan, PTL from MirantisMeeting Summary:1.Migrating to YAQL 1.0 status.PIC: Stan lagunStatus: All commits is on review and not yet merged.New YAQL engine should is fully functional at the moment.Though we need to fix PEP8, it passes all unit tests. The YAQL RC2 is released as soon as all YAQL commits got merged and test.Maybe it is better to set it to >=1.0.0Test with RC2 and if everything work fine do RC2 to be the release and m
ceilometer provides monitoring, metering services, Horizon provides user interface, Barbican provides secret key management services.
The fourth tier is mainly consumer services, so-called consumer services, mainly refers to the fourth tier of services need to use the first three layers of services to work.
The fourth floor mainly includes heat, Magnum, Sahara, Solum and Murano, of which heat mainly provide orchestration services, Magnum mai
Meeting time : 2016.july.12 1:00~2:00Chairperson: Kirill Zaitsev, from MirantisMeeting Summary:1.Action Items ReviewAbout Agent Versionsand TBH I ' ve decided to leave it's the it's it's for this cycle,Since we already have N1 beta releaseTo make it clean and clear for everyone involved.2.Open DiscussionHere are a commit to infra, which adds py27 jobs with Mitaka reqs on master.The idea was to ensure we can install Master Murano on top of Mitaka code.
1. Installing Dib-utilsDib Utils are part of the Diskimage-builder project, but they are also used outside the Diskimage-builder project.Because the cloud-based disk space has overflowed, it is undesirable to push all diskimage-builder to use tools such as Dib-run-part.This project allows consumers to use these tools while running a small package, without the need for additional dependencies.Two ways to install:(1) Pip install Dib-utils(2) pip install Git+git://git.openstack.org/
Mirantis, one of the benchmark companies in the OpenStack field, released the latest MOS 8.0 version in early March 2016. This paper tries to make some inductive analysis based on the public data.1. Version Overview 1.1 overview
Community version: Liberty, the default integrated components include ceilometer,Cinder,Glance,Heat,Horizon, Ironic (first support),Keystone,Murano (an application catalog, fir
Highly Available
Concept
Level
Chen Ben
How to Achieve
Classification
The ha of OpenStack
virtual machine ha
compare
application level ha,heat ha template
component ha
mysql ha
Three ways-master-slave synchronization, Main and Standby mode
three ways of two
first, the basic knowledge of OpenStackOpenStack is a free software and open source project that was developed and initiated by NASA and Rackspace to Apache2.0 licenses (compatible with GPLv3 and DFSG).OpenStack is an open source cloud computing management Platform project, composed of several major components to accomplish specific tasks. OpenStack supports almost all types of cloud environments, and the p
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.