[openstack-dev] [masakari] No masakari meeting on 11/12

Hi all!, Sorry for the late announcement. Since most of us in Berlin summit, there will be no IRC meeting at 11/12. --- Regards, Sampath __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [nova] nova cellsv2 and DBs / down cells / quotas

ces and > calculating quotas. The reaction was (very surprisingly to me) negative > to this option. It seems very low-effort, high-gain, and proper re-use > of existing technologies to me, without us having to replicate a > replication engine (hah) in python. So, I'm curious: does that

Re: [openstack-dev] [nova] nova cellsv2 and DBs / down cells / quotas

> On 24 Oct 2018, at 4:01 pm, melanie witt wrote: > > On Wed, 24 Oct 2018 10:54:31 +1100, Sam Morrison wrote: >> Hi nova devs, >> Have been having a good look into cellsv2 and how we migrate to them (we’re >> still on cellsv1 and about to upgrade to queens and sti

[openstack-dev] [nova] nova cellsv2 and DBs / down cells / quotas

ova+branch:master+topic:bp/handling-down-cell> But what about quota? If a cell goes down then it would seem that a user all of a sudden would regain some quota from the instances that are in the down cell? Just wondering if anyone has thought about this? Cheer

[openstack-dev] [ironic] Stepping down as core

to see you there. The Ironic project has been (and I hope continues to be) an awesome place to contribute too, thank you Sam Betts sambetts __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack

Re: [openstack-dev] [masakari][congress] what is a host?

Hi Eric, (1) "virtual machine" is bug. This need to be corrected as physical machine or hypervisor. Masakari host is a physical host/hypervisor. I will correct this. (2) Not through masakari APIs. You have to add metadata key 'HA_Enabled=True' to each VM by using nova API. Masakeri

[openstack-dev] [masakari] No meeting on next week (9/10)

Hi All, Since most of us in Denver for PTG, there will be not meeting on 9/10. --- Regards, Sampath __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [ironic][bifrost][sushy][ironic-inspector][ironic-ui][virtualbmc] sub-project/repository core reviewer changes

+1 Sam On 23/08/2018, 21:38, "Mark Goddard" mailto:m...@stackhpc.com>> wrote: +1 On Thu, 23 Aug 2018, 20:43 Jim Rollenhagen, mailto:j...@jimrollenhagen.com>> wrote: ++ // jim On Thu, Aug 23, 2018 at 2:24 PM, Julia Kreger mailto:juliaashleykre...@gmail.com>&g

Re: [openstack-dev] [nova][cinder][neutron] Cross-cell cold migration

backed instances and so this is also something to take into account which nova would be responsible for. I’ll be in Denver so we can discuss more there too. Cheers, Sam > On 23 Aug 2018, at 11:23 am, Matt Riedemann wrote: > > Hi everyone, > > I have started an etherpad f

Re: [openstack-dev] [Release-job-failures][masakari][release] Pre-release of openstack/masakari failed

Hi Doug, Thanks. I will fix this. --- Regards, Sampath On Fri, Aug 10, 2018 at 2:51 AM Doug Hellmann wrote: > Excerpts from zuul's message of 2018-08-09 17:23:01 +: > > Build failed. > > > > - release-openstack-python >

Re: [openstack-dev] [tripleo] [tripleo-validations] using using top-level fact vars will deprecated in future Ansible versions

text from untrusted sources is properly handled to defend against this. > I think the last thing we want is to break TripleO + Ceph integration so we > will maintain Ansible 2.5.x in TripleO Rocky and upgrade to 2.6.x in Stein > when ceph-ansible 3.2 is used and working well. This sounds like

Re: [openstack-dev] [tripleo] [tripleo-validations] using using top-level fact vars will deprecated in future Ansible versions

these things as well. --- Respectfully, Sam Doran Senior Software Engineer Ansible by Red Hat sdo...@redhat.com <mailto:sdo...@redhat.com>__ OpenStack Development Mailing List (not for usage questions) Unsubscr

[openstack-dev] [masakari] weekly meeting time changed

Hi All, Gentle reminder about next Masakari meeting time. Form next meeting (5th June), meeting will be start at 0300UTC. Please find more details at [1]. [1] http://eavesdrop.openstack.org/#Masakari_Team_Meeting --- Regards, Sampath

Re: [openstack-dev] [all][ptl][release][masakari][murano][qinling][searchlight][zaqar] reminder for rocky-1 milestone deadline

Hi Doug and ALL, Thank you for the reminder. This was my mistake and really ​s orry for any inconvenience this may have caused. This will not happen again.​​ ​Patches are up to review for following projects.​ > masakari-monitors ​> ​ masakari --- Regards, Sampath On Sat, Apr 21, 2018 at 3:04

Re: [openstack-dev] [masakari] Introspective Instance Monitoring through QEMU Guest Agent

Hi Louie, Thanks for bring this up. I add this topic to today's meeting agenda. --- Regards, Sampath On Tue, Apr 24, 2018 at 5:15 AM, Kwan, Louie wrote: > Submitted the following review on January 17, 2018, > > https://review.openstack.org/#/c/534958/ > > Would

Re: [openstack-dev] [ironic] Monthly bug day?

100% on board with this, I think it was really productive! Sam On 23/04/2018, 15:44, "Jim Rollenhagen" <j...@jimrollenhagen.com<mailto:j...@jimrollenhagen.com>> wrote: On Mon, Apr 23, 2018 at 8:04 AM, Michael Turek <mjtu...@linux.vnet.ibm.com<mailto:mjtu...@lin

Re: [openstack-dev] [TripleO][CI][QA][HA][Eris][LCOO] Validating HA on upstream

Hi All, Sorry, Late to the party... I have added myself. --- Regards, Sampath On Fri, Mar 16, 2018 at 9:31 AM, Ghanshyam Mann wrote: > On Thu, Mar 15, 2018 at 9:45 PM, Adam Spiers wrote: > > Raoul Scarazzini wrote: > >> > >> On

[openstack-dev] [masakari] Rocky work items

Hi All, Rocky work items will be discussed in 3/20 masakari IRC meeting [1]. Current items are listed in etherpad [2] and new items, comments, questions are welcome. If you are not able to join IRC meeting, then please add sufficient details to your comment and your contacts (IRC or email) where

Re: [openstack-dev] [masakari] Masakari Project mascot ideas

ri Project mascot ideas > > > Hi Sampath San, > > > There is one more option which we discussed in yesterdays masakari meeting > [1]: > > St. Bernard(Dog) [2]. > > > [1] http://eavesdrop.openstack.org/meetings/masakari/2018/ > masakari.2018-03-13-04.01.log.html#

Re: [openstack-dev] [masakari] Masakari Project mascot ideas

erdays masakari meeting > [1]: > > St. Bernard(Dog) [2]. > > > [1] http://eavesdrop.openstack.org/meetings/masakari/2018/ > masakari.2018-03-13-04.01.log.html#l-38 > > > [2] https://en.wikipedia.org/wiki/St._Bernard_(dog) > > > Thank you, > > Dinesh Bhor

[openstack-dev] [masakari] Masakari Project mascot ideas

Hi All, We started this discussion on IRC meeting few weeks ago and still no progress..;) ​(aspiers: thanks for the reminder!) Need mascot proposals for Masakari, see FAQ [1] for more info Current ideas: Origin of "Masakari" is related to hero from Japanese folklore [2]. Considering that

Re: [openstack-dev] [masakari] Any masakari folks at the PTG this week ?

Hi All, Really sorry, I couldn't make it to PTG. However, as Dinesh said some team members are at PTG. I can connect on Zoom or Skype or Hangout... etc. Let me know the time if you are meeting up.. Thanks.. --- Regards, Sampath On Thu, Mar 1, 2018 at 8:03 AM, Adam Spiers

Re: [openstack-dev] [masakari] [masakari-monitors] : Intrusive Instance Monitoring through QEMU Guest Agent Design Update

​Hi Louie, Thank you for patch and Sorry for the delay​ response. I prefer ​option 2. >From Masakari point of view, this is an instance event. Because, even if some thing wrong inside the VM, Masakari only can try to fix it by restart, rebuilt, migrate... etc the VM. Which are the same recovery

Re: [openstack-dev] [ironic] Nominating Hironori Shiina for ironic-core

+1 On 09/02/2018, 04:36, "Shivanand Tendulker" > wrote: +1 On Wed, Feb 7, 2018 at 11:53 AM, John Villalovos > wrote: +1 On Mon, Feb 5, 2018 at 10:12 AM, Julia Kreger

Re: [openstack-dev] [OpenStackClient][Security][ec2-api][heat][horizon][ironic][kuryr][magnum][manila][masakari][neutron][senlin][shade][solum][swift][tacker][tricircle][vitrage][watcher][winstackers]

Hi Matthew, Thanks for the info. For Masakari, after discussing with release team, all following 3 project will do independent release for Queens. masakari masakari ​​ masakari-monitorsmasakari python-masakariclient

[openstack-dev] [masakari] Rocky PTL Candidacy

Hello everyone, I’m Sampath Priyankara. I would like to announce my candidacy to continue as PTL of Masakari for the Rocky development cycle. In Queens, we mainly focused on bugfixing, documentation, add new features and become an official OpenStack project which is one of the most important

Re: [openstack-dev] [release][masakari] Need help on masakari deliverables

Hi Sean, Thanks. That make sense. I will proceed masakari release as independent for Queens. And will push those patches to Rocky. --- Regards, Sampath On Thu, Feb 1, 2018 at 12:30 AM, Sean McGinnis <sean.mcgin...@gmx.com> wrote: > On Thu, Feb 01, 2018 at 12:19:16AM +0900, Sa

[openstack-dev] [release][masakari] Need help on masakari deliverables

Hi release team, I did not realize at the time however, I noticed that masakari does not have any of it deliverables are set for Queens in [1]. Which is my fault and really sorry for that. We currently have 3 deliverables, masakari: repos: - openstack/masakari masakari-monitors:

Re: [openstack-dev] [masakari] [Release-job-failures] Tag of openstack/masakari failed

Hi Sean, Thanks for the advice. Above fix has merged. --- Regards, Sampath On Wed, Jan 31, 2018 at 9:39 PM, Sean McGinnis wrote: > Masakari had a release job fail for publishing the release notes. It > appears to > be due to the release notes not being updated to

Re: [openstack-dev] [tc][masakari][api] masakari service-type, docs, api-ref and releasenotes

Hi Monty, Thanks for the patches. Agree that 'ha' is a pretty broad service-type for Masakari. compute-ha or instance-ha are both OK, as Andreas proposed, I would like to change it to instance-ha. If no objections, I will fix the python-masakariclient, devstack pulgin etc.. from masakari

Re: [openstack-dev] [requirements] adding uwsgi to global-requirements

> Original Message > Subject: Re: [openstack-dev] [requirements] adding uwsgi to > global-requirements > Local Time: December 19, 2017 9:57 PM > UTC Time: December 20, 2017 2:57 AM > From: mtrein...@kortar.org > To: Sam Yaple <s...@yaple.net>, OpenSta

Re: [openstack-dev] [requirements] adding uwsgi to global-requirements

> Original Message > Subject: Re: [openstack-dev] [requirements] adding uwsgi to > global-requirements > Local Time: December 19, 2017 6:34 PM > UTC Time: December 19, 2017 11:34 PM > From: mtrein...@kortar.org > To: Sam Yaple <s...@yaple.net>, OpenSta

[openstack-dev] [requirements] adding uwsgi to global-requirements

Hello, I wanted to bring up the idea of getting uwsgi into the requirements repo. I seem to recall this being discussed a couple of years back, but for the life of me I cannot find the thread, so forgive me if I am digging up ancient history. I would like to see uwsgi in

Re: [openstack-dev] [Ironic] Removal of tempest plugin code from openstack/ironic & openstack/ironic-inspector

load both versions of the tempest plugin (from ironic and ironic-tempest-plugin) in a non-deterministic order resulting in non-deterministic results from your CI. Sam On 19/12/2017, 16:54, "John Villalovos" <openstack@sodarock.com<mailto:openstack@sodarock.com>> wr

[openstack-dev] [nova] Listing servers with filters and policy

ndling as opposed to just whether you’re admin or not. Thanks! Sam __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.o

Re: [openstack-dev] [kolla] Ansiblize init-runonce script

For what its worth, this init-runonce script was never meant for production usage. Ops *shouldn't* be running it like you suggest. It was historically for use in the gate and a quick-n-dirty environment setup for testing. If you want to get into writing operations scripts, thats your

Re: [openstack-dev] Building Openstack Trove Images

As Amrith stated, you need to look at the Neutron logs as the message about port binding suggests: PortBindingFailed: Binding failed for port 26b727dd-52b4-4b34-b484-6ea3fd571c8d, please check neutron logs for more information. On Mon, Nov 13, 2017 at 8:22 AM, Debojyoti Das

Re: [openstack-dev] [masakari] A current high-level description of masakari architecture

Hi Greg, [1] is pretty out-of-date, and [2] much closer what we have now. Plus, I am updating [2] with current details, for Masakari Project On boarding session. I will update the wiki and share the slides soon. Till then, [2] is the best options we have now.. [1]

Re: [openstack-dev] [QA][LCOO] MEX-ops-meetup: OpenStack Extreme Testing

other tool or mix of them) can analyze the result and create the final report. Sorry for ranting. --- Regards, Sampath On Wed, Nov 1, 2017 at 4:02 PM, Boris Pavlovic <bo...@pavlovic.me> wrote: > Sam, > >> Etherpad: https://etherpad.openstack.org/p/SYD-extreme-testing > &

Re: [openstack-dev] [QA][LCOO] MEX-ops-meetup: OpenStack Extreme Testing

"OpenStack Development Mailing List (not for usage questions)" > <openstack-dev@lists.openstack.org> > Cc: openstack-operators <openstack-operat...@lists.openstack.org> > Subject: Re: [openstack-dev] [QA][LCOO] MEX-ops-meetup: OpenStack Extreme > Testing > > > >

Re: [openstack-dev] Fwd: [Openstack-operators][tc] [keystone][all] v2.0 API removal

The Keystone v2 removal also broke Trove's gate. Trove's functional and scenario tests had Keystone v2 hard codings and also relied on a > 4 year old 'compat' client package in the python-troveclient that did not have V3 support. Both cases required a lot of scrambling find all the v2 hard

Re: [openstack-dev] Fwd: [Distutils][pbr][devstack][qa] Announcement: Pip 10 is coming, and will move all internal APIs

On Fri, Oct 20, 2017 at 4:32 PM, Doug Hellmann wrote: > Excerpts from Clark Boylan's message of 2017-10-20 13:14:13 -0700: > > On Fri, Oct 20, 2017, at 11:17 AM, Clark Boylan wrote: > > > On Fri, Oct 20, 2017, at 07:23 AM, Doug Hellmann wrote: > > > > It sounds like the

Re: [openstack-dev] [TripleO][Kolla] Concerns about containers images in DockerHub

On Thu, Oct 19, 2017 at 11:23 PM, Gabriele Cerami <gcer...@redhat.com> wrote: > On 19 Oct, Sam Yaple wrote: > > So it seems tripleo is building *all* images and then pushing them. > > Reworking your number leads me to believe you will be consuming 10-15GB > in > > to

Re: [openstack-dev] [TripleO][Kolla] Concerns about containers images in DockerHub

On Thu, Oct 19, 2017 at 9:38 PM, Gabriele Cerami <gcer...@redhat.com> wrote: > On 19 Oct, Sam Yaple wrote: > > docker_image wouldn't be the best place for that. Buf if you are looking > > for a quicker solution, kolla_docker was written specifically to be > license >

Re: [openstack-dev] [TripleO][Kolla] Concerns about containers images in DockerHub

docker_image wouldn't be the best place for that. Buf if you are looking for a quicker solution, kolla_docker was written specifically to be license compatible for openstack. its structure should make it easily adapted to delete an image. And you can copy it and cut it up thanks to the license.

Re: [openstack-dev] [all][infra] Zuul v3 rollout, the sequel returns

Thanks. I will try to fix the legacy-trove-functional. On Sat, Oct 14, 2017 at 12:58 AM, Andreas Jaeger <a...@suse.com> wrote: > On 2017-10-14 03:30, Sam Matzek wrote: >> The legacy-trove-functional-dsvm-mysql and >> legacy-trove-legacy-functional-dsvm-mysql jobs

Re: [openstack-dev] [all][infra] Zuul v3 rollout, the sequel returns

details and links to the zuulv3-issues etherpad. I'm not familiar enough with the job definitions to be able to work on the fix reviews for these but would like to learn. Sam Matzek On Fri, Oct 13, 2017 at 2:57 PM, Jeremy Stanley <fu...@yuggoth.org> wrote: > The tl;dr is that we're

Re: [openstack-dev] [all][tc] TC Candidates: what does an OpenStack user look like?

I used to be able to say "my OpenStack background is in Operations" but that isn't strictly true anymore. I've now spent the majority of my time doing what is considered 'developer' work. One thing is for certain though, I have never stopped building OpenStack for what I see as the "hypothetical

Re: [openstack-dev] [ironic] How is the interface for tftpboot server typically configured on OVS ?

need to scale up our Ironic services, I can replicate the same trunk and sub-interface on each conductor server assigning a different one of the reserved IPs to each, letting our ironic services happily scale up horizontally as intended. Sam On 12/10/2017, 23:42, "Waines, Greg"

[openstack-dev] [masakari] Propose changes of the core team

Hi All Masakari Cores, I would like to propose following changes to Masakari core team. Current core team: Masahito Muroi Rikimaru Honjo Sampath Priyankara (samP) Takashi Kajinami Toshikazu Ichikawa Tushar Patil Yukinori Sagara (A) Proposed to remove from Core team: (1) Toshikazu Ichikawa He

[openstack-dev] [all][masakari] Masakari accepted into official projects

Hi All, I am happy to announce that Masakari [1] (Instances High Availability Service) has become official OpenStack from last week[2]. I would like to take this opportunity to thank, all Masakari contributors for your hard work over the past years, and all OpenStack community members for

Re: [openstack-dev] [ptls] Sydney Forum Project Onboarding Rooms

Hi Kendall, Thank you.. --- Regards, Sampath On Thu, Oct 12, 2017 at 1:57 AM, Kendall Nelson <kennelso...@gmail.com> wrote: > Hello :) > > Congrats! I added you/Masakari to my list. > > -Kendall (diablo_rojo) > > On Wed, Oct 11, 2017 at 12:28 AM Sam P <sam47pr

Re: [openstack-dev] [ptls] Sydney Forum Project Onboarding Rooms

Hi Kendall, Thank you for info. If slots are still available, we would like to do an On-boarding session for Masakari [1]. # BTW, got the TC approval yesterday [2]... [1] https://wiki.openstack.org/wiki/Masakari [2] https://review.openstack.org/#/c/500118/ --- Regards, Sampath On Wed, Oct

Re: [openstack-dev] [ironic] Proposing Shivanand Tendulker for ironic-core

+1, Sam On 03/10/2017, 08:21, "tua...@vn.fujitsu.com<mailto:tua...@vn.fujitsu.com>" <tua...@vn.fujitsu.com<mailto:tua...@vn.fujitsu.com>> wrote: +1 , Yes, I definitely agree with you. Regards Tuan From: Nisha Agarwal [mailto:agarwalnisha1...@gmail.com] Sent: Tue

Re: [openstack-dev] [infra][devstack][congress] zuul3 transition surfaced error: The following LIBS_FROM_GIT were not installed correct: python-congressclient

This is also one of several errors hitting the Trove gate. This review should workaround the issue for now. https://review.openstack.org/#/c/508344/3 On Mon, Oct 2, 2017 at 1:44 PM, Eric K wrote: > Since the transition to zuul3, this error began and prevents the

Re: [openstack-dev] [masakari] No IRC meeting this week

Hi All, We are planning to have meeting on Sep 14 Thursday 4:00-5:00pm in Ballroom C in PTG venue. Place and time might change suddenly. In that case I will send updates to this thread. --- Regards, Sampath On Mon, Sep 11, 2017 at 7:05 PM, Sam P <sam47pr...@gmail.com> wrote: &g

[openstack-dev] [masakari] No IRC meeting this week

Hi All, As we discussed in our last week IRC meeting, there will be no IRC meting today. I will check the possible/available space in PTG venue and send details for PTG meetup. [1] is the agenda for the meeting. [1] https://etherpad.openstack.org/p/masakari-queens-workitems --- Regards, Sampath

Re: [openstack-dev] [tc][masakari] new project teams application for Masakari

ilability? > > Tim > > -Original Message- > From: Sam P <sam47pr...@gmail.com> > Reply-To: "OpenStack Development Mailing List (not for usage questions)" > <openstack-dev@lists.openstack.org> > Date: Friday, 1 September 2017 at 19:27 > To: "Ope

[openstack-dev] [tc][masakari] new project teams application for Masakari

Hi All, I have just proposed inclusion of Masakari[1] (Instances High Availability Service) into list of official OpenStack projects in [2]. Regarding this proposal, I would like to ask OpenStack community for what else can be improved in the project to meet all the necessary requirements. And I

Re: [openstack-dev] [Openstack-operators] [kolla][puppet][openstack-ansible][tripleo] Better way to run wsgi service.

I have been running api services behind uwsgi in http mode from Newton forward. I recently switched to the uwsgi+nginx model with 2 containers since I was having wierd issues with things that I couldn't track down. Mainly after I started using keystone with ldap. There would be timeouts and

Re: [openstack-dev] [ironic] [release] [stable] pike release

Quick reply with my thoughts in-line. Sam On 21/08/2017, 10:13, "Dmitry Tantsur" <dtant...@redhat.com> wrote: (adding the release and stable team just for their information) Thanks Julia and everyone for handling this situation while I was out. More

Re: [openstack-dev] [masakari]I withdraw my remark of today's IRC meerting.

Hi Rikimaru, Thank you for verification. --- Regards, Sampath On Tue, Aug 15, 2017 at 7:37 PM, Rikimaru Honjo wrote: > Hello, > > In today's Masakari IRC meeting, I said that executing masakari notification > API was failed in the latest devstack

[openstack-dev] [masakari] Make 'error' instances recovery configurable

Hi Dinesh and Rikimaru, It seems that Dinesh[1] and Rikimaru [2] pushed a patch to fix same issue. Thank you for your effort. Please discuss and merge them into one patch. [1] https://review.openstack.org/#/c/493534/ [2] https://review.openstack.org/#/c/493476/ --- Regards, Sampath

[openstack-dev] [QA][LCOO] MEX-ops-meetup: OpenStack Extreme Testing

Hi All, This is a follow up for OpenStack Extreme Testing session[1] we did in MEX-ops-meetup. Quick intro for those who were not there: In this work, we proposed to add new testing framework for openstack. This framework will provides tool for create tests with destructive scenarios which will

Re: [openstack-dev] [requirements][masakari] FFE for adding python-masakariclient in global-requirements

Hi Tony, Thanks. > - Abandon: https://review.openstack.org/457491 > - Merge : https://review.openstack.org/492965 Done. --- Regards, Sampath On Sat, Aug 12, 2017 at 8:13 AM, Tony Breeds <t...@bakeyournoodle.com> wrote: > On Fri, Aug 11, 2017 at 12:23:12AM -0500, Sam P wr

Re: [openstack-dev] [requirements][masakari] FFE for adding python-masakariclient in global-requirements

to get merged. [1] https://review.openstack.org/#/c/457491 [2] https://review.openstack.org/#/c/491692/ --- Regards, Sampath On Thu, Aug 10, 2017 at 11:59 PM, Sam P <sam47pr...@gmail.com> wrote: > Hi Tony, > > As you suggested, I would like go with option 1. > >> Once

Re: [openstack-dev] [requirements][masakari] FFE for adding python-masakariclient in global-requirements

rt.. --- Regards, Sampath On Thu, Aug 10, 2017 at 7:08 PM, Tony Breeds <t...@bakeyournoodle.com> wrote: > On Thu, Aug 10, 2017 at 12:58:21PM -0500, Sam P wrote: >> Hi Tony, >> >> For maskari-monitors, earliest we can cut stable/pike is 8/11. >> You was mention

Re: [openstack-dev] [masakari]Remove ERROR instances from recovery targets

Hi Rikimaru, Currently, [1] does not skip error instances from evacuating. However, it does make it back to error after evacuating the instance. If your requirement does not satisfied with that, then the next option will be create a option for not to evacuate error VMs first place. Because,

Re: [openstack-dev] [requirements][masakari] FFE for adding python-masakariclient in global-requirements

Hi Tony, For maskari-monitors, earliest we can cut stable/pike is 8/11. You was mentioned about masakari and related projects in [1]. For python-masakariclient, stable/pike can be cut on 8/11. However, for maskari I would like to land few changes before cut stable/pike and hopefully we can cut

Re: [openstack-dev] [ironic] Looking for a good end-to-end demo of ironic integrated within openstack

Information about the ironic deployment process including full workflows can be found here: https://docs.openstack.org/ironic/latest/user/index.html#deploy-process Sam On 28/07/2017, 12:49, "Waines, Greg" <greg.wai...@windriver.com<mailto:greg.wai...@windriver.com>> wrot

Re: [openstack-dev] [ironic] Looking for a good end-to-end demo of ironic integrated within openstack

the default images loaded by devstack, I believe by default it downloads them from the cirros http://download.cirros-cloud.net Sam On 24/07/2017, 17:07, "Waines, Greg" <greg.wai...@windriver.com<mailto:greg.wai...@windriver.com>> wrote: Hey Lucas, Thanks for the pointer to this

Re: [openstack-dev] [masakari]Where is the masakari-monitors spec repository?

Hi Honjo, There are no dedicated spec repositories for masakari-monitors and python-masakariclient. Please use the masakari-spec repository[1] for spec discussion for those 2 projects. [1] https://review.openstack.org/#/q/project:openstack/masakari-specs --- Regards, Sampath On Fri, Jul

Re: [openstack-dev] [ironic] Routed Networks, flat driver and physical network awareness

that scheduling gives you a valid baremetal node when you request a baremetal instance on a routed network. Any help and/or reviews of this work would be most appreciated, Sam Betts (sambetts) On 28/06/2017, 10:31, "Harald Jensås" <hjen...@redhat.com> wrote: Hi, With the f

Re: [openstack-dev] [vitrage] [nova] [HA] [masakari] VM Heartbeat / Healthcheck Monitoring

Hi Vikash, Greg submit the spec [1] for intrusive instance monitoring. Your review will be highly appreciated.. [1] https://review.openstack.org/#/c/469070/ --- Regards, Sampath On Sat, May 20, 2017 at 4:49 PM, Vikash Kumar <vikash.ku...@oneconvergence.com> wrote: > T

Re: [openstack-dev] [masakari] Intrusive Instance Monitoring

Hi Greg, Great.. thank you. I will ask people to review this.. --- Regards, Sampath On Tue, May 30, 2017 at 9:06 PM, Waines, Greg <greg.wai...@windriver.com> wrote: > Hey Sam, > > > > Was able to submit the blueprint and spec. > > > > Blueprint: > https

Re: [openstack-dev] [masakari] Intrusive Instance Monitoring

Hi Greg, # Thank you Jeremy..! I couldn't find any problem with repo side. As Jeremy pointed out, could you please check the `git remote show gerrit`. BTW, could you please create a BP in [1] and link it to your spec when you commit it. In this way, we could track all the changes related to

Re: [openstack-dev] [ironic] [tripleo] [dib] RFC: moving/transitioning the ironic-agent element to the ironic-python-agent tree

for the element, I think that is more intuitive anyway. An RFE or multiple might be useful for tracking this work. Sam On 22/05/2017, 13:40, "Dmitry Tantsur" <dtant...@redhat.com> wrote: Hi all! Some time ago we discussed moving ironic-agent element that is used to build IPA

Re: [openstack-dev] [vitrage] [nova] [HA] [masakari] VM Heartbeat / Healthcheck Monitoring

use gerrit for this git ? >> >> Do you have a template for your specs ? >> >> >> >> Greg. >> >> >> >> >> >> >> >> From: Sam P <sam47pr...@gmail.com> >> Reply-To: "openstack-dev@lists.openstack.org" >

Re: [openstack-dev] [vitrage] [nova] [HA] [masakari] VM Heartbeat / Healthcheck Monitoring

: > Yes I am good with writing spec for this in masakari-spec. > > > > Do you use gerrit for this git ? > > Do you have a template for your specs ? > > > > Greg. > > > > > > > > From: Sam P <sam47pr...@gmail.com> > Reply-To: &q

Re: [openstack-dev] [masakari] Intrusive Instance Monitoring

Hi Greg, Thank you for proposal. #BTW, I replied to our discussion in [1]. Masakari mainly focuses on black box monitoring the VMs. But that does not mean Masakari do not do white box type of monitoring. There will be a configuration options for operators for whether to use it or not and

Re: [openstack-dev] [vitrage] [nova] [HA] [masakari] VM Heartbeat / Healthcheck Monitoring

h - ... >> - VNF-Manager >> >> - (StateChange) - Nova - ... - VNF Manager >> >> >> Greg. >> >> >> From: Adam Spiers <aspi...@suse.com<mailto:aspi...@suse.com>> >> Reply-To: >> "openstack-dev@lists.openstack.org&

Re: [openstack-dev] [tc][infra][release][security][stable][kolla][loci][tripleo][docker][kubernetes] do we want to be publishing binary container images?

I would like to bring up a subject that hasn't really been discussed in this thread yet, forgive me if I missed an email mentioning this. What I personally would like to see is a publishing infrastructure to allow pushing built images to an internal infra mirror/repo/registry for consumption of

Re: [openstack-dev] [vitrage] [nova] VM Heartbeat / Healthcheck Monitoring

Hi Greg, In Masakari [0] for VMHA, we have already implemented some what similar function in masakri-monitors. Masakari-monitors runs on nova-compute node, and monitors the host, process or instance failures. Masakari instance monitor has similar functionality with what you have described.

Re: [openstack-dev] [FaaS] Introduce a FaaS project

Hi Larry, Thank you for the details. I am interested and like the idea of no vendor/platform lock-in. However, I still have this stupid question in me. Why FaaS need to be in the OpenStack ecosystem? Can it survive outside and still be able to integrate with OpenStack? This FaaS must able

Re: [openstack-dev] [HA] HA Discussion at Boston Forum

-HA-in-openstack Please join and let's discuss the HA issues in OpenStack... --- Regards, Sampath On Mon, Apr 10, 2017 at 12:37 PM, Sam P <sam47pr...@gmail.com> wrote: > Hi All, > > I proposed a session [1] to Boston Forum and it is now at incomplete state. > This is good o

Re: [openstack-dev] 答复: [Openstack] 答复: OpenStack-Ansible HA solution

o kind of you if you can touch Masakari team. > > Thank you again! > > Best Regards! > Maxwell Li > maxwelli.com > > -邮件原件- > 发件人: Sam P [mailto:sam47pr...@gmail.com] > 发送时间: 2017年4月28日 0:16 > 收件人: OpenStack Development Mailing List (not for usage questions) &

Re: [openstack-dev] [Openstack-operators] [nova][glance] Who needs multiple api_servers?

on Openstack install where you want to control the traffic. I can understand using the catalog in certain situations and feel it’s OK for that to be the default but please don’t prevent operators configuring it differently. Glance is the big one as you want to cont

Re: [openstack-dev] [User-committee] [Forum] Moderators needed!

Hi Arkandy, Thank you. I replied to Shamail with "I am available to moderate the session" for ​ High Availability in OpenStack . However, by mistake my reply only sent to individual

Re: [openstack-dev] [Openstack] 答复: OpenStack-Ansible HA solution

Hi Maxwell, As John mentioned, current OSA does not support Masakri. However, if it make your work easier, then I would love to discuss this with Masakri team [1]. [1] https://wiki.openstack.org/wiki/Meetings/Masakari --- Regards, Sampath On Thu, Apr 27, 2017 at 10:39 PM, John Petrini

[openstack-dev] [HA] HA Discussion at Boston Forum

Hi All, I proposed a session [1] to Boston Forum and it is now at incomplete state. This is good opportunity for all of us to get together and discuss our HA related issues. I need your help to reform this session. Please put comments on [1] or replay to this with your comments. [1]

Re: [openstack-dev] [Openstack] How to get all detail RPC message and detail context in neutron docs?

Thank you, use debug option will also help us to get detail of RPC message, good luck~ 2017-04-06 14:20 GMT+08:00 김기석 [Kiseok Kim] <ks...@netmarble.com>: > Sam, > > > > I have no idea whether or not the document exists. (I want to read too) > > > > about L3

Re: [openstack-dev] [Openstack] How to get all detail RPC message and detail context in neutron docs?

For example, detail of the messages of topics.L3_AGENT 2017-04-06 9:38 GMT+08:00 Sam <batmanu...@gmail.com>: > Thank you all. > > For 'context', I got it. > For RPCs, is there some document or blog or some debug method to get its > detal contains in neutron L3 Agent? >

Re: [openstack-dev] [Openstack] How to get all detail RPC message and detail context in neutron docs?

Thank you all. For 'context', I got it. For RPCs, is there some document or blog or some debug method to get its detal contains in neutron L3 Agent? 2017-04-06 9:33 GMT+08:00 김기석 [Kiseok Kim] <ks...@netmarble.com>: > Hi Sam, > > > > that 'context' is olso_co

[openstack-dev] How to get all detail RPC message and detail context in neutron docs?

Hi all, I'm working on neutron L3 Agent and some other Agent. I found that there are lots of RPCs including RPC call and notification and lots of 'context' as bellow. But I don't know its detail context, can I get these from some docs? If there are no docs, could I get these using some debug

[openstack-dev] How to find "ovs_mechanism + vxlan tanent_type_driver + L2_pop" configure steps?

Hi all, In openstack-ocata install docs, I only found "linux_bridge + vxlan + l2pop" configure steps, Is there "ovs+vxlan+l2pop" configure steps? Thank you~ __ OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] Is there some way to run specific unittest in neutron?

Thank you all 2017-03-23 13:41 GMT+08:00 Kevin Benton <ke...@benton.pub>: > tox -epy27 test_ovs_neutron_agent > > On Mar 22, 2017 22:25, "Sam" <batmanu...@gmail.com> wrote: > >> Hi all, >> >> I'm working on neutron, I add

[openstack-dev] Is there some way to run specific unittest in neutron?

Hi all, I'm working on neutron, I add some code into ovs_neutron_agent.py, and I extend test_ovs_neutron_agent.py. Is there some way to run test_ovs_neutron_agent.py or run related module only? Thank you. __ OpenStack

Re: [openstack-dev] [kolla] rabbitmq cluster_partition_handling config in kolla-ansible

ything but 'autoheal' for OpenStack specifically. I certainly don't see any advantages. Now that the ask has been made though, a variable would be 2 lines of code in total, so I say go for it. Thanks, SamYaple Sam Yaple On Mon, Mar 20, 2017 at 2:43 PM, Nikita Gerasimov < nikita.gerasi...@o

[openstack-dev] Fwd: How to fix this bug?

Hi all, I'm installing openstack ocata version, in this step: https://docs.openstack.org/ocata/install-guide-ubuntu/keystone-users.html I got error while run 'openstack' command: Unauthorized: The request you have made requires authentication. (HTTP 401) (Request-ID:

Re: [openstack-dev] [Neutron] ImportError: No module named neutron_lib

Sorry, it's oslo_db, I'm wrong 2017-03-09 14:22 GMT+08:00 Sam <batmanu...@gmail.com>: > I found this: > > from oslo_config import ... > from oslo_db import ... > from neutron_lib import ... > > actually these libraries is oslo.config, oslo.db, neutron.lib > &

  1   2   3   4   >