Re: [openstack-dev] [Openstack-sigs] [all][tc] We're combining the lists! (was: Bringing the community together...)

On Thu, Sep 20, 2018 at 2:48 PM Doug Hellmann wrote: > > Excerpts from Jeremy Stanley's message of 2018-09-20 16:32:49 +: > > tl;dr: The openstack, openstack-dev, openstack-sigs and > > openstack-operators mailing lists (to which this is being sent) will > > be replaced by a new openstack-disc

[openstack-dev] [chef] fog-openstack 0.3

Ohai! fog-openstack 0.3 has been released upstream, but it also seems to be a breaking release by way of naming convention. At this time, it is advised to pin your client cookbook at '<0.3.0'. Changes to compensate for this change are being delivered to git and Supermarket, but the most immediate

Re: [openstack-dev] [election][tc]Question for candidates about global reachout

e to being able to justify an hour to a conference room or an office to further the intent of openness in the community. I directly see the benefit in having a means to reach the greater community (hi! o/) but I do not directly see the

Re: [openstack-dev] [election][tc]Question for candidates about global reachout

here as opposed to IRC. The continuation of this thread only confirms that there is already fragmentation in the community, and that people on each side of the void genuinely want to close that gap. At this point, the thing t

Re: [openstack-dev] [election][tc]Question for candidates about global reachout

what happens when otherwise diverse communities enter into a freemium contract. The net result is that people communicate less and less for various reasons, ending in the inverse of the desired effect of being more connected. Best, Samuel _

Re: [openstack-dev] [Openstack-sigs] Open letter/request to TC candidates (and existing elected officials)

up' phrase, creates an effect where people do not carve out enough time to effect change, becoming too busy, repeat ad infinitum. Best, Samuel __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: op

Re: [openstack-dev] [tripleo] VFs not configured in SR-IOV role

Adding the following to neutron-sriov.yaml solved the problem OS::TripleO::Services::NeutronSriovHostConfig: ../../puppet/services/neutron-sriov-host-config.yaml On Wed, Sep 12, 2018 at 11:53 AM Samuel Monderer < smonde...@vasonanetworks.com> wrote: > Hi Saravanan, > > I'm

Re: [openstack-dev] [tripleo] VFs not configured in SR-IOV role

Hi Saravanan, I'm using RHOSP13. The neutron-sriov-agent.yaml is missing "OS::TripleO::Services::NeutronSriovHostConfig" Regards, Samuel On Fri, Sep 7, 2018 at 1:08 PM Saravanan KR wrote: > Not sure which version you are using, but the service > "OS::TripleO::Servic

Re: [openstack-dev] [election][tc] Opinion about 'PTL' tooling

actor in deeply human-driven interactions can have ramifications immediately noticed. As distributed as things exist today, reducing the conversation to a few methods or people can damage intent, without humans talking to humans in a more direct manner. Best, Samuel Cassiba (scas)

Re: [openstack-dev] [election] [tc] TC candidacy

On Fri, Sep 7, 2018 at 8:55 AM, Samuel Cassiba wrote: > On Fri, Sep 7, 2018 at 6:22 AM, Matt Riedemann wrote: >> On 9/5/2018 2:49 PM, Samuel Cassiba wrote: >>> >>> Though my hands-on experience goes back several releases, I still view >>> things from the ou

Re: [openstack-dev] [election] [tc] TC candidacy

On Fri, Sep 7, 2018 at 6:22 AM, Matt Riedemann wrote: > On 9/5/2018 2:49 PM, Samuel Cassiba wrote: >> >> Though my hands-on experience goes back several releases, I still view >> things from the outside-looking-in perspective. Having the outsider >> lens is cruci

[openstack-dev] [election] [tc] TC candidacy

ent in the overall conversations that drive so much of our daily lives. At the end of the day, we're all just groups of people trying to do our jobs. I view this as an opportunity to give back to a community that has given me so much. Thank you for your attention and consideration, Samuel Cassiba (s

[openstack-dev] [chef] State of the Kitchen: 7th Edition

ter 2 hours, remove the steak from the water bath and pat very dry with paper towels. 6. Heat oil in a medium cast iron skillet over high heat until it shimmers. 7. Add steak and sear until well-browned, about 30 seconds per side. 8. Let rest for 5 minutes. 9. Enjoy. Your humble line cook, S

[openstack-dev] [tripleo] VFs not configured in SR-IOV role

Hi, Attached is the used to deploy an overcloud with SR-IOV role. The deployment completed successfully but the VFs aren't configured on the host. Can anyone have a look at what I missed. Thanks Samuel <> _

Re: [openstack-dev] [tripleo] using multiple roles

Is it possible to have the roles_data.yaml file generated when running "openstack overcloud deploy"?? On Tue, Sep 4, 2018 at 4:52 PM Alex Schultz wrote: > On Tue, Sep 4, 2018 at 2:31 AM, Samuel Monderer > wrote: > > Hi, > > > > Due to many different HW in our

[openstack-dev] [tripleo] using multiple roles

Hi, Due to many different HW in our environment we have multiple roles. I would like to place each role definition if a different file. Is it possible to refer to all the roles from roles_data.yaml to all the different files instead of having a long roles_data.yaml file? Regards, Samuel

Re: [openstack-dev] [chef] fog-openstack 0.2.0 breakage

On Fri, Aug 31, 2018 at 8:59 AM, Samuel Cassiba wrote: > Ohai! > > fog-openstack 0.2.0 was recently released, which had less than optimal > effects on Chef OpenStack due to the client cookbook's lack of version > pinning on the gem. > Currently, the client cookbook is pinn

[openstack-dev] [chef] Retiring openstack/openstack-chef-repo

lease. It no longer tests cleanly due to the detritus of time, so it will remain in its current state. The retirement festivities can be found at https://review.openstack.org/#/q/topic:retire-openstack-chef-repo If you have any questions or concerns, please don't hesitate to reach ou

[openstack-dev] [chef] fog-openstack 0.2.0 breakage

Ohai! fog-openstack 0.2.0 was recently released, which had less than optimal effects on Chef OpenStack due to the client cookbook's lack of version pinning on the gem. The crucial change is that fog-openstack itself now determines Identity API versions internally, in preparation for a versionless

Re: [openstack-dev] [goals][python3][adjutant][barbican][chef][cinder][cloudkitty][i18n][infra][loci][nova][charms][rpm][puppet][qa][telemetry][trove] join the bandwagon!

| 5 repos | > On behalf of Chef OpenStack, that one is good to go. Best, Samuel (scas) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] Stepping down as keystone core

coordinator for OpenStack. Let me know if you are interested on one of those things. Get in touch on #openstack-outreachy, #openstack-sdks or #openstack-keystone. Thanks, Samuel de Medeiros Queiroz (samueldmq) __ OpenStack

Re: [openstack-dev] Stepping down as coordinator for the Outreachy internships

Hi all, As someone who cares for this cause and participated twice in this program as a mentor, I'd like to candidate as program coordinator. Victoria, thanks for all your lovely work. You are awesome! Best regards, Samuel On Thu, Aug 9, 2018 at 6:51 PM Kendall Nelson wrote: > You h

[openstack-dev] [tripleo] deployements fails when using custom nic config

ploy_stderr: | Heat Stack create failed. Heat Stack create failed. (undercloud) [stack@staging-director ~]$ When I checked the controller node I found that it had no default gateway configured Regards, Samuel contr

[openstack-dev] [tripleo] network isolation!!! do we still need to configure VLAN , CIDR, ... in network-environment.yaml

6.0.250'}] # Leave room if the external network is also used for floating IPs ExternalAllocationPools: [{'start': '192.168.204.6', 'end': '192.168.204.99'}] In queens now that we use nerwork_data.yaml do we still need to set the parameters above? Samu

[openstack-dev] [chef] State of the Kitchen: 6th Edition

with forks until it doesn't look like mustard 6. Serve with dippin' sause, or use it as drownin' sause 7. Enjoy Your humble line cook, Samuel Cassiba (scas) __ OpenStack Development Mailing List (not for usage ques

Re: [openstack-dev] [all] Ongoing spam in Freenode IRC channels

On Wed, Aug 1, 2018 at 5:21 AM, Andrey Kurilin wrote: > I can make an assumption that for marketing reasons, Slack Inc can propose > extended Free plan. > But anyway, even with default one the only thing which can limit us is > `10,000 searchable messages` which is bigger than 0 (freenode doesn't

Re: [openstack-dev] [tripleo] deployement fails

I used the same host network configuration I used with Ocata (see attached) Do I need to change them if I'm deploying queens?? Thanks, Samuel On Tue, Jul 31, 2018 at 7:06 PM Alex Schultz wrote: > On Mon, Jul 30, 2018 at 8:48 AM, Samuel Monderer > wrote: > > Hi, > > >

[openstack-dev] [tripleo] overcloud deployment fails with during keystone configuration

Hi, My overcloud deployment fails with the following error 2018-07-31 14:20:23Z [overcloud.AllNodesDeploySteps.ControllerDeployment_Step3]: CREATE_FAILED Resource CREATE failed: Error: resources[0]: Deployment to server failed: deploy_status_code : Deployment exited with non-zero status code: 2 2

Re: [openstack-dev] [tripleo] deployement fails

Removing it just made it longer to time out On Mon, Jul 30, 2018 at 7:51 PM, Remo Mattei wrote: > Take it off and check :) > > > > On Jul 30, 2018, at 09:46, Samuel Monderer > wrote: > > Yes > I tried eith 60 and 120 > > On Mon, Jul 30, 2018, 19:42 Remo

Re: [openstack-dev] [tripleo] deployement fails

Yes I tried eith 60 and 120 On Mon, Jul 30, 2018, 19:42 Remo Mattei wrote: > Do you have a timeout set? > > > On Jul 30, 2018, at 07:48, Samuel Monderer > wrote: > > > > Hi, > > > > I'm trying to deploy a small environment with one controller a

[openstack-dev] [tripleo] deployement fails

alues | {u'interface_name': u'nic1', u'bridge_name': u'br-ex'} | | action| CREATE | +---++ (undercloud) [stack@staging-director ~]$ Regards, Samuel __ OpenStack Development Mailing List (not

Re: [openstack-dev] [tripleo] network isolation can't find files referred to on director

ID for the internal_api network traffic. type: number I worked fine when I was using RHOSP11(Ocata) The custom_network_data.yaml defines the internal network as following - name: InternalApi name_lower: internal_api vip: true vlan: 711 ip_subnet: '172.16.2.0/24' allocation_

[openstack-dev] [chef] PTL candidacy for Stein

Howdy! I am submitting my name to continue as PTL for Chef OpenStack. If you don't know me, I am scas on Freenode. I work for Workday, where I am an active operator and upstream developer. I have contributed to OpenStack since 2014, and joined the Chef core team in early 2015. Since then, I have s

Re: [openstack-dev] [tripleo] network isolation can't find files referred to on director

bout custom nic configs is there also a jinja2 process to create them? Samuel On Thu, Jul 26, 2018 at 12:02 AM James Slagle wrote: > On Wed, Jul 25, 2018 at 11:56 AM, Samuel Monderer > wrote: > > Hi, > > > > I'm trying to upgrade from OSP11(Ocata) to OSP13 (Queens) >

[openstack-dev] [tripleo] Setting swift as glance backend

Hi, I would like to deploy a small overcloud with just one controller and one compute for testing. I want to use swift as the glance backend. How do I configure the overcloud templates? Samuel __ OpenStack Development

[openstack-dev] [tripleo] network isolation can't find files referred to on director

-heat-templates/network/ports/noop.yaml OS::TripleO::Compute::Ports::TenantPort: /usr/share/openstack-tripleo-heat-templates/network/ports/tenant.yaml OS::TripleO::Compute::Ports::ManagementPort: /usr/share/openstack-tripleo-heat-templates/network/ports/management_from_pool.yaml Where have they gone? S

Re: [openstack-dev] [tripleo] Mistral workflow cannot establish connection

ipleO::Controller::Ports::ManagementPort: /usr/share/openstack-tripleo-heat-templates/network/ports/management_from_pool.yaml* Have they moved to a different location or are they created during the overcloud deployment?? Thanks Samuel On Mon, Jul 16, 2018 at 3:06 PM Steven Hardy wrote: > On Sun, Jul

Re: [openstack-dev] [tripleo] Mistral workflow cannot establish connection

" from the deployment script the deployment passes the point it was failing before but fails much later because of the missing definition of the role. Samuel On Sun, Jul 15, 2018 at 8:35 PM Remo Mattei wrote: > I still think there is something wrong with some of your yaml, the > roles_data

Re: [openstack-dev] [tripleo] Mistral workflow cannot establish connection

It seems that the problem is in my roles_data.yaml file but I don't see what is the problem I've attached the file. On Sun, Jul 15, 2018 at 12:46 AM Remo Mattei wrote: > It is a bad line in one of your yaml file. I would check them. > > Sent from my iPad > > On Jul 14,

[openstack-dev] [tripleo] Mistral workflow cannot establish connection

-ae4yIf/tripleo-heat-templates Unable to establish connection to https://192.168.50.30:13989/v2/action_executions: ('Connection aborted.', BadStatusLine("''",)) (undercloud) [root@staging-director stack]# Couldn't find any

[openstack-dev] [chef] State of the Kitchen: 5th Edition

your preferred choice of thickener. Use cornstarch or flour if you're not super carb-conscious. Hit it with the immersion blender. 7. Return shredded meat to what could be misconstrued as gravy. Salt to taste and dig in. It gets better if you leave it overnight in the fridge t

Re: [openstack-dev] [all] [release] How to handle "stable" deliverables releases

On Mon, Jun 11, 2018 at 2:53 AM, Thierry Carrez wrote: > > 2bis/ Like 2, but only create the branch when needed > > Same as the previous one, except that rather than proactively create the > stable branch around release time, we'd wait until the branch is actually > needed to create it. > This is

Re: [openstack-dev] [tc][all] A culture change (nitpicking)

bad by > leaving them with the 'credit' for my bad work, so it's important to be > careful and tactful. But the history is public record, at least. > > If the patch is bad enough where I have to step in to rewrite, I'm making the submitter look bad no matter what

Re: [openstack-dev] [tc] Organizational diversity tag

nal diversity tag seems more a symptom of unwellness in what is being measured, not necessarily irrelevance of the metric. Measuring in terms of throughput and number of contributors is one thing, but the outcome of the measure needs to feed back into better maintainership for the overall health of Ope

[openstack-dev] [chef] State of the Kitchen: 4th Edition

xture 6. Heat the cream cheese in the microwave, add the cream and mix. Pour mixture over the casserole. 7. Mix ingredients until incorporated. Overmixing will give a more pate-like texture. 8. Bake @ 350F / 176C for 40 minutes. Your humble l

Re: [openstack-dev] [tripleo] cannot configure host kernel-args for pci passthrough with first-boot

# Note this is new-for-kilo, an alternative is returning a value then using # get_attr in the parent template instead. OS::stack_id: value: {get_resource: userdata} Samuel On Tue, May 22, 2018 at 8:05 AM Saravanan KR wrote: > Could you check the log in the /var/log/cloud-init-output.log file

[openstack-dev] [chef] State of the Kitchen - 3rd Edition

food processor. Blend until desired consistency, or until you do not see pieces of jalapeno. Your humble line cook, Samuel Cassiba (scas) __ OpenStack Development Mailing List (not for usage questions) Unsubscrib

[openstack-dev] [chef] State of the Kitchen - 2nd Edition

in with a fork. Your humble cook, Samuel Cassiba __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [chef] Pike cookbooks released

Chef 13, with Chef 12 now being unsupported in master. If you need to use an older release of OpenStack with Chef 13, this will give you a blueprint for what needs to be backported. Prost! Your humble cook, Samuel Cassiba (sc` / scas

[openstack-dev] [chef] State of the Kitchen - 1st Edition

and sour cream to tame the heat. Apply baby wipes when appropriate. Gets hotter overnight. Your humble cook, Samuel Cassiba (sc` / scas) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: ope

[openstack-dev] [chef][ptl] PTL candidacy for Rocky

rts look elsewhere for an upstream. Thank you for reading. Delightfully, Samuel Cassiba __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe h

[openstack-dev] [chef] Heads up - Chef 13 is incoming

always open. Just keep in mind that the team is very distributed, so park a client for a while. -- Best, Samuel Cassiba __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ

Re: [openstack-dev] [Tripleo] Composable role OVS-DPDK compute node with single NIC

http://paste.openstack.org/show/626557/ On Tue, Nov 21, 2017 at 8:22 PM Ben Nemec wrote: > Your configuration lost all of its indentation, which makes it extremely > difficult to read. Can you try sending it a different way, maybe > paste.openstack.org? > > On 11/16/2017 0

[openstack-dev] [Tripleo] Composable role OVS-DPDK compute node with single NIC

/sysconfig/network-scripts/route-br-ex Samuel OsNetConfigImpl: type: OS::Heat::StructuredConfig properties: group: os-apply-config config: os_net_config: network_config: - type: ovs_user_bridge name: {get_input: bridge_name} use_dhcp: false dns_servers: {get_param: DnsServers} addresses: -

Re: [openstack-dev] Upstream LTS Releases

, and some are, but it's pretty damned daunting from the outside. The new contributors who want to contribute but don't see the way in, probably because we haven't said mellon, are left scratching their heads and eventual

Re: [openstack-dev] [Openstack-operators] Upstream LTS Releases

On Fri, Nov 10, 2017 at 2:51 PM, John Dickinson wrote: > What I heard from ops in the room is that they want (to start) one release a > year who's branch isn't deleted after a year. What if that's exactly what we > did? I propose that OpenStack only do one release a year instead of two. We > still

Re: [openstack-dev] Upstream LTS Releases

On Wed, Nov 8, 2017 at 11:17 AM, Doug Hellmann wrote: > Excerpts from Samuel Cassiba's message of 2017-11-08 08:27:12 -0800: >> On Tue, Nov 7, 2017 at 3:28 PM, Erik McCormick >> wrote: >> > Hello Ops folks, >> > >> > This morning at the Syd

Re: [openstack-dev] Upstream LTS Releases

ow that the proposition exists about making a Stable Release liaison derived from existing cores, I can't help but get the impression that, for active-but-quiet projects, it'll be yet another PTL responsibility to keep up with, in addition t

Re: [openstack-dev] [ptg] Simplification in OpenStack

nStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Best, Samuel Cassiba signature.asc Description: Message signed with OpenPGP

Re: [openstack-dev] [ptg] Simplification in OpenStack

al would be great- easier said than done of course. > > Samuel, > Default configuration as I envision it != "Promoting a single solution". I > really hope a working default install would allow new users to get started > with OpeStack without promoting anything. OpenStac

Re: [openstack-dev] [ptg] Simplification in OpenStack

> On Sep 25, 2017, at 16:52, Clint Byrum wrote: > > Excerpts from Jonathan D. Proulx's message of 2017-09-25 11:18:51 -0400: >> On Sat, Sep 23, 2017 at 12:05:38AM -0700, Adam Lawson wrote: >> >> :Lastly, I do think GUI's make deployments easier and because of that, I >> :feel they're critical.

Re: [openstack-dev] [ptg] Simplification in OpenStack

gt;> > I’m taking a break >> > from the room at the moment for lunch, but I encourage people at 13:30 >> > local time to meet >> > at the simplification room level b in the big thompson room. Thank you! >> > >> > — >> > Mike Perez >>

[openstack-dev] [chef] stable/ocata has been released

been beneficial. For any issues, or just to say hi, feel free to drop by #openstack-chef and idle. Onward to Pike! -- Best, Samuel Cassiba __ OpenStack Development Mailing List (not for usage questions) Unsubscribe

Re: [openstack-dev] [chef] Proposing Lance Albertson (Ramareth) for openstack-chef-core

On Tue, Aug 8, 2017 at 7:24 PM, Samuel Cassiba wrote: > Ohai! > > In openstack-chef-land, we generally don't use the ML very often, > being so few; thus, when there's an occasion to send something, it > better be worth it. > > I am proposing adding Lance Albertson

[openstack-dev] [chef] Proposing Lance Albertson (Ramareth) for openstack-chef-core

d Ruby, but the quirks of OpenStack and Python. However, we do what we can, when we can, how we can. Any feedback is welcome. If there are no reasons otherwise, Lance will be added to the core group in a few days. -- Best,

Re: [openstack-dev] [all][tc] How to deal with confusion around "hosted projects"

t get that memo until the Big Tent was deemed too smothering. The fun part about being a PTL with effectively no team is that, when you or your counterpart isn’t actively marketing and spending more time making noise than working,

Re: [openstack-dev] EXT: [octavia] scheduling webex to discuss flavor spec (https://review.openstack.org/#/c/392485/)

Carlos, We are in Israel and would like the meeting to happen at a more favorable time to us, for example 9:00AM CDT. -Sam. From: Carlos Puga [mailto:carlos.p...@walmart.com] Sent: Monday, June 26, 2017 7:04 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openst

Re: [openstack-dev] [all][tc] Moving away from "big tent" terminology

pstream. “If it ain’t broke, don’t fix it” is still a strong force to contend with, whether we like it or not. Providing smooth, clear paths to a production-grade open cloud should be the aim, not what the definition of is, is, even if that is what comes naturally to groups of highly skilled, highl

Re: [openstack-dev] [tc][fuel] Making Fuel a hosted project

ious path forward, save for “lol deal with it". From my point of view, we mustn’t lose sight of that just because a given project doesn’t have enough throughput, or enough developers, just because a vendor moves on to something newer and shinier. > > Best, > -jay

Re: [openstack-dev] [all][stable][ptls] Tagging mitaka as EOL

Hi Tony, I’m not the PTL, but I asked in our channel. You can EOL Chef OpenStack as well. Thanks! -- Best, Samuel Cassiba signature.asc Description: Message signed with OpenPGP __ OpenStack Development Mailing List (not

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

> On Feb 15, 2017, at 08:49, Alex Schultz wrote: > > On Wed, Feb 15, 2017 at 9:02 AM, Samuel Cassiba wrote: >>> On Feb 15, 2017, at 02:07, Thierry Carrez wrote: >>> >>> Samuel Cassiba wrote: >>>> [...] >>>> *TL;DR* if you don'

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

> On Feb 15, 2017, at 02:07, Thierry Carrez wrote: > > Samuel Cassiba wrote: >> [...] >> *TL;DR* if you don't want to keep going - >> OpenStack-Chef is not in a good place and is not sustainable. >> [...] > > Thanks for sharing, Sam. > Thanks fo

[openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

The HTML version is here: https://s.cassiba.com/2017/02/14/making-the-kitchen-great-again-a-retrospective-on-openstack-chef This was influenced by Graham Hayes' State of the Project for Designate:

[openstack-dev] [keystone] PTL candidacy

uring our first PTG in Atlanta. I am looking forward to seeing you there! Thank you, Samuel de Medeiros Queiroz - samueldmq [1] https://review.openstack.org/#/c/424239/ __ OpenStack Development Mailing List (not for usage ques

Re: [openstack-dev] [all][stable][ptls] Tagging liberty as EOL

> > On Dec 19, 2016, at 14:31, Tony Breeds wrote: > > On Mon, Dec 19, 2016 at 09:18:20AM -0800, Samuel Cassiba wrote: > >> The Chef OpenStack cookbooks team is way late to the party. The cookbooks >> (openstack/cookbook-openstack-*, openstack/openstack-chef-repo

Re: [openstack-dev] [all][stable][ptls] Tagging liberty as EOL

tack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev The Chef OpenStack cookbooks team is way late to the party. The cookbooks (openstack/

Re: [openstack-dev] [kolla][tc] Video Meetings - input requested

> On Dec 13, 2016, at 19:43, Ed Leafe wrote: > > On Dec 12, 2016, at 10:30 PM, Steven Dake (stdake) wrote: > >> The issue raised is they violate the 4 opens. > > Not necessarily. If you have regular planning meetings and discussions in an > open manner as prescribed, an occasional conference

Re: [openstack-dev] [keystone] Pike PTL

Hey Steve, Thanks for all your dedication, you've been a great leader! It's been a pleasure to serve keystone with you as PTL. Samuel On Tue, Nov 29, 2016 at 12:19 PM, Brad Topol wrote: > +1! Great job Steve > > > Brad Topol, Ph.D. > IBM Distinguished Engineer >

[openstack-dev] [chef] draft logo & sneak peek

. Since neither myself nor the other cores will be at the PTG, we’ll have to work out some way to get the final product distributed if interested. Have a great Summit! Best, Samuel Cassiba Project Team Lead, OpenStack Chef > Begin forwarded message: > > From: Heidi Joy Tretheway > S

Re: [openstack-dev] [rpm-packaging][chef][puppet][salt][openstack-ansible][HA][tripleo][kolla][fuel] Schema proposal for config file handling for services

d may lead to issues on the user >>> side when ordering is a problem or attempting to debug issues. I think >>> this can lead to more issues than it's solving. >> >> Most services print the complete config when running in debug mode. So >> getting th used config

Re: [openstack-dev] [chef] Adding calbers to openstack-chef-core

gt; Jan > >> On 05 Oct 2016, at 05:44, Samuel Cassiba wrote: >> >> Ohai Chefs! >> >> I would like to nominate Christoph Albers (irc: calbers) for >> openstack-chef-core. >> >> Christoph has consistently provided great quality reviews over the >

[openstack-dev] [chef] Adding calbers to openstack-chef-core

Ohai Chefs! I would like to nominate Christoph Albers (irc: calbers) for openstack-chef-core. Christoph has consistently provided great quality reviews over the Newton cycle. He has been instrumental in getting the cookbooks up to speed with Identity v3 and openstackclient. During Mitaka, his rev

[openstack-dev] [chef] Chef PTL candidacy

ensure that people can get started deploying OpenStack and hacking on cookbooks. I look forward to continuing to steer the OpenStack Chef cookbooks as well as collaborating with other projects within the greater OpenStack project. Yours, Samuel Cassiba [0]

[openstack-dev] [keystone] PTL candidacy

workflows, and e) making the default RBAC authorization more granular. Thank you, Samuel de Medeiros Queiroz [1] https://review.openstack.org/#/c/369002/ __ OpenStack Development Mailing List (not for usage questions) Unsubscribe

Re: [openstack-dev] [keystone] new core reviewer (rderose)

Ronald, congrats, well deserved! Welcome aboard! On Thu, Sep 1, 2016 at 11:56 AM, David Stanek wrote: > On Thu, Sep 01 at 10:44 -0400, Steve Martinelli wrote: > > > > Thanks for all your hard work Ron, we sincerely appreciate it. > > > > Contrats! Well deserved for sure! > > -- > David Stanek >

Re: [openstack-dev] Reasoning behind my vote on the Go topic

On 6/7/16 12:00 PM, Monty Taylor wrote: [snip] > I'd rather see us focus energy on Python3, asyncio and its pluggable event loops. The work in: http://magic.io/blog/uvloop-blazing-fast-python-networking/ is a great indication in an actual apples-to-apples comparison of what can be accomplishe

Re: [openstack-dev] [tc] supporting Go

On 5/11/16 7:09 AM, Thomas Goirand wrote: On 05/10/2016 09:56 PM, Samuel Merritt wrote: On 5/9/16 5:21 PM, Robert Collins wrote: On 10 May 2016 at 10:54, John Dickinson wrote: On 9 May 2016, at 13:16, Gregory Haynes wrote: This is a bit of an aside but I am sure others are wondering the

Re: [openstack-dev] [tc] supporting Go

On 5/9/16 5:21 PM, Robert Collins wrote: On 10 May 2016 at 10:54, John Dickinson wrote: On 9 May 2016, at 13:16, Gregory Haynes wrote: This is a bit of an aside but I am sure others are wondering the same thing - Is there some info (specs/etherpad/ML thread/etc) that has more details on the b

Re: [openstack-dev] [all] Newton Summit: cross-project session for deployment tools projects

On Thu, Mar 31, 2016 at 2:40 PM, Emilien Macchi wrote: > Hi, > > OpenStack big tent has different projects for deployments: Puppet, > Chef, Ansible, Kolla, TripleO, (...) but we still have some topics in > common. > I propose we use the Cross-project day to meet and talk about our > common topic

Re: [openstack-dev] [chef] ec2-api cookbook

On Thu, Mar 24, 2016 at 11:25 AM, Ronald Bradford wrote: > Samuel, > > Could you detail when your IRC meeting is, [1] indicates it's on Tuesdays. > > [1] https://wiki.openstack.org/wiki/Meetings/EC2API > > Regards > > Ronald > > On Thu, Mar 24, 2016 at 1

Re: [openstack-dev] [chef] ec2-api cookbook

ge questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > Hi Anastasia, That's great news! We'll have to go through the process of getting a new repo added under our project. Would you be able

Re: [openstack-dev] [swift] Can swift identify user agent come from chrome browser?

On 3/17/16 1:53 AM, Linpeimin wrote: Hello, everyone. I have config a web server (tengine) as a proxy server for swift, and sent a GET request via a chrome browser in order to access swift container. From the log file, it can be seen that web server has pass the request to swift, but swift retur

[openstack-dev] [chef] PTL Candidacy

oordination and maintaining strong lines of communication. I would greatly appreciate your support for PTL, if you'll have me, and I'm looking forward to growing the Chef OpenStack team. The official elections review is here: https://review.openstack.org/#/c/29

Re: [openstack-dev] Reg: Configuration Management tool for Openstack.

You can also use Chef for either a small-scale or production level deployment. Check out https://wiki.openstack.org/wiki/Chef/GettingStarted for a bit more context, or if you just want to jump in head-first https://github.com/openstack/openstack-chef-repo/blob/master/README.md On Thu, Mar 10, 201

Re: [openstack-dev] [Neutron][LBaaS]Removing LBaaS v1 - are weready?

]Removing LBaaS v1 - are weready? Ok, for what it’s worth we have contributed our migration script: https://review.openstack.org/#/c/289595/ — please look at this as a starting point and feel free to fix potential problems… Thanks, German On 3/7/16, 11:00 AM, "Samuel Bercovici" wrote: &g

Re: [openstack-dev] [Neutron][LBaaS]Removing LBaaS v1 - are weready?

o change their IPs… Thanks, German On 3/6/16, 5:35 AM, "Samuel Bercovici" wrote: >As for a migration tool. >Due to model changes and deployment changes between LBaaS v1 and LBaaS v2, I >am in favor for the following process: > >1. Download LBaaS v1 information (Tenan

Re: [openstack-dev] [Neutron][LBaaS]Removing LBaaS v1 - are weready?

different VIPs so the end user would need to change their IPs… Thanks, German On 3/6/16, 5:35 AM, "Samuel Bercovici" wrote: >As for a migration tool. >Due to model changes and deployment changes between LBaaS v1 and LBaaS v2, I >am in favor for the following process: >

Re: [openstack-dev] [Neutron][LBaaS]Removing LBaaS v1 - are weready?

> [sbaluk...@bluebox.net<mailto:sbaluk...@bluebox.net>] > Sent: Wednesday, March 02, 2016 4:49 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [Neutron][LBaaS]Removing LBaaS v1 - are weready? > > I am also on-board with remo

Re: [openstack-dev] [Neutron][LBaaS]Removing LBaaS v1 - are weready?

anywhere. Thanks, doug On Mar 2, 2016, at 7:06 AM, Samuel Bercovici mailto:samu...@radware.com>> wrote: Hi, I have just notices the following change: https://review.openstack.org/#/c/286381 which aims to remove LBaaS v1. Is this planned for Mitaka or for Newton? While LBaaS v2 is becom

[openstack-dev] [Neutron][LBaaS]Removing LBaaS v1 - are we ready?

Hi, I have just notices the following change: https://review.openstack.org/#/c/286381 which aims to remove LBaaS v1. Is this planned for Mitaka or for Newton? While LBaaS v2 is becoming the default, I think that we should have the following before we replace LBaaS v1: 1. Horizon Support -

  1   2   3   >