+1
Regards,
Saravanan KR
On Fri, Oct 19, 2018 at 5:53 PM Juan Antonio Osorio Robles
wrote:
>
> Hello!
>
>
> I would like to propose Bob Fournier (bfournie) as a core reviewer in
> TripleO. His patches and reviews have spanned quite a wide range in our
> project, his revie
.
Regards,
Saravanan KR
On Sat, Sep 22, 2018 at 4:52 AM Janki Chhatbar wrote:
>
> Hi All
>
> As per the discussion at PTG, I have filed a BP [1]. I will push a spec
> sometime around mid-October.
>
> [1]. https://blueprints.launchpad.net/tripleo/+spec/automatic-role-generation
>
&g
Not sure which version you are using, but the service
"OS::TripleO::Services::NeutronSriovHostConfig" is responsible for
setting up VFs. Check if this service is enabled in the deployment.
One of the missing place is being fixed -
https://review.openstack.org/#/c/597985/
Regards,
Sarav
Are you using the first-boot script [1] mapped to NodeUserData? If
yes, you could check the logs/error of the first-boot script
@/var/log/cloud-init-output.log on the overcloud nodes.
Regards,
Saravanan KR
[1]
https://github.com/openstack/tripleo-heat-templates/blob
+1
Regards,
Saravanan KR
On Wed, Jun 13, 2018 at 9:20 PM, Emilien Macchi wrote:
> Alan Bishop has been highly involved in the Storage backends integration in
> TripleO and Puppet modules, always here to update with new features, fix
> (nasty and untestable third-party backends) bugs a
l to allow heat merging to work
https://review.openstack.org/#/c/448209
Regards,
Saravanan KR
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:u
Could you check the log in the /var/log/cloud-init-output.log file to
see what are the first-boot scripts which are executed on the node?
Add "set -x" in the kernel-args.sh file to better logs.
Regards,
Saravanan KR
On Tue, May 22, 2018 at 12:49 AM, Samuel Monderer
wrote:
> Hi,
&
;qemu:hugetlbfs"
user and group. So to avoid conflicts of running different group on
different roles of a TripleO deployment, I prefer to update the qemu
group as "hugetlbfs" for all the nodes of all roles, if DPDK is
enabled in the deployment.
Let us know if you see a
On Fri, Nov 24, 2017 at 10:09 PM, Alex Schultz wrote:
> On Fri, Nov 24, 2017 at 5:03 AM, Saravanan KR wrote:
>> Hello,
>>
>> For dpdk in ovs2.8, the default permission of vhost user ports are
>> modified from root:root to openvswitch:hugeltbfs. The vhost user
>>
er if we can add
ansible based configuration along with docker-puppet for any new
modules going forward. But I am not sure of the direction.
Prefer the feedback before proceeding with an approach.
Regards,
Saravanan KR
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1515269
[2] https://github.c
,
Saravanan KR
[1]
https://docs.openstack.org/tripleo-docs/latest/install/advanced_deployment/role_specific_parameters.html
[2]
https://github.com/openstack/tripleo-heat-templates/blob/master/puppet/services/neutron-ovs-dpdk-agent.yaml#L59
On Tue, Nov 21, 2017 at 4:46 PM, Giulio Fidente wrote:
>
network and DPDK as Tenant network [1] which will have the
tenant and vlan configured directly on the bridge (this configuration
was recommended from the ovs team).
>> > Second the default route on control plane is not set even though
>> it is
>> > configured in
arameters, which are accepted as role-specific. The next step is to
add a validation to role-specific parameters.
Regards,
Saravanan KR
[1] https://review.openstack.org/#/c/506133/
[2] https://review.openstack.org/#/c/517231/
__
O
As discussed in IRC, I have collated all the important discussions to
the etherpad (gdoc was not publicly shareable).
https://etherpad.openstack.org/p/tripleo-derive-parameters-v2
Lets continue discussion on the etherpad to finalize.
Regards,
Saravanan KR
On Thu, Nov 9, 2017 at 11:05 AM
+1
Regards,
Saravanan KR
On Thu, Nov 9, 2017 at 11:40 AM, Emilien Macchi wrote:
> Of course +1, thanks for your hard work! Stay awesome.
> ---
> Emilien Macchi
>
> On Nov 9, 2017 4:58 PM, "Marios Andreou" wrote:
>>
>>
>>
>> On Thu, Nov 9, 2017
rame for this
workflow?
>
> 6/ Advanced deployment config - a view providing a way to review
> Environment/Roles/Services parameters, search and tweak them if needed.
>
> 7/ Deploy.
>
> I believe these steps should cover anything we should need to do for
> deployme
, list of parameters, its types, and its default values (and
choices if present), are required
Did I miss anything?
Regards,
Saravanan KR
[1]
https://github.com/openstack/tripleo-heat-templates/blob/master/plan-samples/plan-environment-derived-params.yaml
On Wed, Nov 8, 2017 at 2:39 PM, Bogdan
Thanks for initiating Brent. Yes, I would participate in the networking squad.
Regards,
Saravanan KR
On Mon, Oct 16, 2017 at 6:43 PM, Brent Eagles wrote:
> Hi,
>
> On Tue, Oct 10, 2017 at 10:55 AM, Brent Eagles wrote:
>>
>> Hi all,
>>
>> The list of TripleO sq
VF. It seem it requires additional reboot for the
> SR-IOV VFs to be created. Is that expected behavior? Am I doing something
> wrong?
The file allocate_vfs is required for the subsequent reboots, but
during the deployment, the vfs are created by puppet-tripleo [1]. No
additional reboot r
config file instead.
Definitely it will be good for upgrade to keep the same uid/gid so
that existing DPDK based VMs continue to work after upgrade.
But any other specific reasons for sticking with same qemu uid/gid in
kolla
d deployment. I am planning to ensure
that kolla's user id (42427) is updated to the host via the host prep
tasks. Let me know if there is any other aspects to be considered.
Regards,
Saravanan KR
[1]
https://github.com/openstack/kolla/blob/187b1f08f586327e5c47a0bed3760a575daa1287/kolla/com
es, or re-implement the os-net-config logic in template
> to get the physical interface name. The latter one will be a repetitive work
> of os-net-config.
This patch [1] has been started by Dan Sneddon to provide the nic
number to name mapping by providing an extra option "--interfaces
Thank you for your support.
Regards,
Saravanan KR
On Mon, Jul 31, 2017 at 7:19 PM, Emilien Macchi wrote:
> On Fri, Jul 21, 2017 at 8:01 AM, Emilien Macchi wrote:
>> Saravanan KR has shown an high level of expertise in some areas of
>> TripleO, and also increased his involvemen
| NeutronL3HA
The next step is to add a warning (or rather error) message if a
deployment contains a parameter which is not part of the plan
(including custom templates). I will work on it.
Regards,
Saravanan KR
[1]
http://logs.openstack.org/77/479277/6/check-tripleo/gate-tripleo-ci-centos-7-ovb
Regards,
Saravanan KR
>
> Best Regards,
> Don
>
> On Thu, Jul 6, 2017 at 4:10 AM, Saravanan KR wrote:
>>
>> Hello,
>>
>> DPDK is integrated with TripleO deployment during the newton cycle.
>> From then on, we used to get queries on how to decide the
eeds to be looked is that, should it be associated
with containers upgrade? May be OVN and ODL can be migrated as
containers only instead of baremetal by default (just a thought, could
have implications to be worked/discussed out).
Regards,
Saravanan KR
[1]
https://github.com/openstack/
ost at the last leg with the help from many folks.
Following are the list of patches pending:
https://review.openstack.org/#/c/480525/ (tripleoclient)
https://review.openstack.org/#/c/468989/ (tripleo-common)
https://review.openstack.org/#/c/471462/ (tripleo-common)
Regards,
Saravanan KR
the group, to bring
awareness on the parameter deprecation.
Regards,
Saravanan KR
[1] https://review.openstack.org/#/c/463949/
[2] https://review.openstack.org/#/c/463941/
__
OpenStack Development Mailing List (not for usage
ervice, it has to brought up
individually/separately, with the dependency of openvswitch. I am
still getting familiar with the blocks around this.
I will be updating the analysis and the progress, any suggestions or
directions is more than welcome.
Regards,
Saravanan KR
[1] https://review.opensta
patch for doing it in tripleo-common [2]. The
output of this flattening will look like [3][4].
I am not sure if this is what you are expecting.
Regards,
Saravanan KR
[1]
https://github.com/openstack/tripleo-common/blob/master/tripleo_common/actions/parameters.py#L71
[2] https://review.openstack.org
the a
parent yam file? Why to add one extra step. May be we can provide all
options in the list and say enabled as 0 or 1. Much simpler to use.
This external tool can be an mistral action to derive the final roles
list internally.
Regards,
Saravanan KR
On Thu, Mar 16, 2017 at 3:37 AM, Emilien
ec/ovs-2-6-features-dpdk
And thanks for the confirmation.
Regards,
Saravanan KR
On Mon, Feb 13, 2017 at 9:36 PM, Emilien Macchi wrote:
> On Wed, Feb 8, 2017 at 1:59 AM, Saravanan KR wrote:
>> Hello,
>>
>> We have raised 2 BP for OvS2.6 integration with DPDK support.
&
deployment.
The change in the resource dependency has been updated in the commit
message.
Please provided your feedback on this approach.
Regards,
Saravanan KR
[1]
https://github.com/openstack/tripleo-heat-templates/blob/master/puppet/compute-role.yaml#L364
[2]
https://github.com/openstack
to be straight forward and minor. And the required
changes has been updated on the BP description. Please let us know if
it requires a spec.
Regards,
Saravanan KR
__
OpenStack Development Mailing List (not for usage questions
we will end up with the same problem, and
definitely, it actually depends on how the features will be composed
on a role. Looking forward.
Regards,
Saravanan KR
On Mon, Jan 23, 2017 at 6:25 PM, Giulio Fidente wrote:
> On 01/23/2017 11:07 AM, Saravanan KR wrote:
>> Thanks John for the info
st as optional parameters
* read introspection data from Ironic DB and Swift-stored blob
I will add these comments as starting point on the spec. We will work
towards bringing down the differences, so that operators headache is
reduced to a greater extent.
Regards,
Saravanan KR
On Fri, Jan 20, 2017
Thanks John, I would really appreciate if you could tag me on the
reviews. I will do the same for mine too.
Regards,
Saravanan KR
On Wed, Jan 11, 2017 at 8:03 PM, John Fulton wrote:
> On 01/11/2017 12:56 AM, Saravanan KR wrote:
>>
>> Thanks Emilien and Giulio for your valuable f
it yet. If it
works out, I will update the etherpad.
Regards,
Saravanan KR
On Wed, Jan 11, 2017 at 5:10 AM, Giulio Fidente wrote:
> On 01/04/2017 09:13 AM, Saravanan KR wrote:
>>
>> Hello,
>>
>> The aim of this mail is to ease the DPDK deployment with TripleO. I
>&g
iables per role. For now, consider this proposal for
homogeneous cluster, if there is a value in this, I will work towards
heterogeneous clusters too.
Please share your thoughts.
Regards,
Saravanan KR
[1] https://krsacme.github.io/blog/post/dpdk-pmd-cpu-list/
[2] https://review.openstack.org/#/c/
uired in the overcloud image, as the "deploy steps" will be
run by the IPA itself.
Regards,
Saravanan KR
[1]
https://github.com/openstack/ironic-python-agent/blob/master/ironic_python_agent/extensions/image.py#L136
On Tue, Dec 13, 2016 at 4:18 PM, Oliver Walsh wrote:
> Hi Y
ot;deploy steps" can
configure this "tuned" setting and run the command, then it is good
enough.
Regards,
Saravanan KR
On Tue, Dec 13, 2016 at 1:04 PM, Yolanda Robla Mota wrote:
> Hi Saravanan
> Thanks for your comments. With this new module, I guess a reboot is still
> ne
you think for/against it.
Regards,
Saravanan KR
On Fri, Dec 2, 2016 at 9:31 PM, Yolanda Robla Mota wrote:
> Hi , Dmitry
> That's what i didn't get very clear. If all the deployment steps are
> pre-imaging as that statement says, or every deploy step could be isolated
> an
node.
If anyone has a better way of doing it, you are more than welcome to suggest.
Regards,
Saravanan KR
[1] https://gist.github.com/krsacme/1234bf024ac917c74913827298840c1c
On Wed, Jul 27, 2016 at 6:52 PM, Saravanan KR wrote:
> Hello,
>
> We are working on SR-IOV & DPDK tripleo int
ng CI queue), we require an FFE (for n3). Please let us
know if you need more details.
Regards,
Saravanan KR
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstac
tions?
Regards,
Saravanan KR
Note: It is possible to use isolcpus via grub parameter, but it has
implications [3] on load balancing. So it is recommended to use
CPUAffinity to restrict CPUs for host process.
[1]
https://www.freedesktop.org/software/systemd/man/systemd-system.conf.html#CPUAffinit
uge pages.
As discussed on the IRC tripleo meeting, we need to ensure that the
user data with update of kernel args, does not overlap with any other
puppet configurations. Please let us know if you have any comments on
this approach.
Regards,
Saravanan KR
[1] https://review.openstack.org/#/c/331
Just to add a point, we are *still* working on dpdk. And this is not
the final code. It may grow a little. We are looking in to adaption
networking-ovs-dpdk puppet code into the agreeable format as
vswitch::dpdk. We would be glad to work with Sean in this process.
Regards,
Saravanan KR
On Fri
Thanks Emilien. I definitely agree with the preference for (1). It is
simpler in choosing either vswitch::ovs or vswitch::dpdk for the
deployment.
Regards,
Saravanan KR
On Fri, Jul 8, 2016 at 5:15 PM, Emilien Macchi wrote:
> On Fri, Jul 8, 2016 at 2:33 AM, Saravanan KR wrote:
>> Also,
uppet-dpdk'.
Regards,
Saravanan KR
[1] https://github.com/openstack/networking-ovs-dpdk
On Fri, Jul 8, 2016 at 2:36 AM, Russell Bryant wrote:
>
>
> On Thu, Jul 7, 2016 at 5:12 AM, Saravanan KR wrote:
>>
>> Hello,
>>
>> We are working on blueprint [1] to int
. It is in progress.
Please let us know your views on including this new module.
Regards,
Saravanan KR
[1] https://blueprints.launchpad.net/tripleo/+spec/tripleo-ovs-dpdk
[2] https://github.com/krsacme/puppet-dpdk
__
OpenStack D
Thanks Matthias for educating me. As there is no universal solution to
this issue, I will check if launch instance page strategy will work out
for this case.
Regards,
Saravanan KR
On 11/04/2015 03:47 PM, Matthias Runge wrote:
On 04/11/15 09:25, Saravanan KR wrote:
There may be multiple
e synchronous and then respond
2) Do not trigger page refresh and respond with Operation in progress
3) If there is a mechanism to know delete in progress, do not list the
interface
To decide on the solution, it is important to know how 202 responses
should be handled. Can anyone can help with un
52 matches
Mail list logo
