date:20170717

[opnfv-tech-discuss] Topics for this week's Technical Community call

2017-07-17 Thread Raymond Paik

All,

I'm reaching out to solicit topics for this week's Technical Community call
(I'm filling in for Bin while he's on vacation).

I already have the topic

from Bryan, but please let me know if there are others.

Thanks,

Ray
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [release][danube] OPNFV Danube 3.0 has been released

2017-07-17 Thread David McBride

TSC members,

I'm pleased to let you know that OPNFV Danube 3.0 has been released.
Software and documentation may be found here
.

Congratulations to everyone in the community that worked hard to make this
release happen.  Please let me know if you have questions or comments.

David

-- 
*David McBride*
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: dmcbr...@linuxfoundation.org
Skype: davidjmcbride1
IRC: dmcbride
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] Lab as a Service - Installer Support

2017-07-17 Thread Lincoln Lavoie

Hi QiLiang,

Some answer inline below, at least for how we've set stuff up so far.



On Mon, Jul 17, 2017 at 11:56 AM, liangqi (D)  wrote:

> I can give some support from compass side. Also I'm recently working on
> opnfv installers' quickstart wrapper scripts( https://gerrit.opnfv.org/
> gerrit/#/c/36711/ ). Hope the scipts could ease developers/users better
> use the labaas resources.
>
>
>
> Here are three questions, after checked the wiki page:
>
> - How do the Laas resources allocated? Allocated as vpods pool and
> BM(1+3+2) pods pool?
>
We have systems setup to allow two virtual pods per hardware node to run in
the lab.  This is based on RAM/Disk/etc.  Access to a pod resource would be
scheduled through the Pharos dashboard system.


> - How do the vpods' and BM jumpserver's operating systems installed,
> manually pre installed by lab admin or auto installed trigger by jenkins
> when the pod is allocated?
>
We've built up some scripts and support to allow the virtual pod to be
"spun up" by the request through the dashboard.  This isn't actually hooked
up to Jenkins, if I understand it correctly, it's its own thing.  We are
trying to keep the system admin out of the request path.  This does depend
on the installer supporting a virtual deployment and a "hands off"
deployment approach.

This will likely start with basic requests, i.e. one 1 or 2 scenarios
supported and go out from there.  We're also planning a developer version,
where the actual OPNFV deployment doesn't occur, so the developer can login
and pull their own artifacts onto the system to deploy from, etc.  Because
the systems are self contained and "throw away."  We'll be able to give
root access onto the environment for each Pod User.  At the end of the
Pod's lifetime, it just gets deleted.


> - Do laas pods share the same jenkins master with other opnfv pods or the
> laas will host a jenkins master to manage all the laas resources?
>
No, see above.


>
>
> Regards,
> QiLiang
> --
> *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [
> opnfv-tech-discuss-boun...@lists.opnfv.org] on behalf of Luke Hinds [
> lhi...@redhat.com]
> *Sent:* Monday, July 17, 2017 22:39
> *To:* opnfv-tech-discuss
> *Subject:* [opnfv-tech-discuss] Lab as a Service - Installer Support
>
> Dear Installer Projects,
>
> I have an action from the infra-wg to gauge which installers can support
> LaaS.
>
> Please peruse the following wiki link for more details on the effort.
>
> https://wiki.opnfv.org/display/INF/Lab+as+a+Service
>
> Recommend you go over the work flow in detail, and consider if you have
> interfaces that can accept the requests and process deployment status.
>
> Any question, please ask over this email or attend the infra-wg group.
>
> Many Thanks,
>
> Luke
>
> --
> Luke Hinds | NFV Partner Engineering | Office of Technology | Red Hat
> e: lhi...@redhat.com | irc: lhinds @freenode | m: +44 77 45 63 98 84 | t: +44
> 12 52 36 2483
>
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>
>


-- 
***
*Lincoln Lavoie*
Senior Engineer, Broadband Technologies


www.iol.unh.edu
21 Madbury Rd., Ste. 100, Durham, NH 03824
Mobile: +1-603-674-2755
lylav...@iol.unh.edu
   


Ars sine scientia nihil est! -- Art without science is nothing.
Scientia sine ars est vacua! -- Science without art is empty.
***
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] Lab as a Service - Installer Support

2017-07-17 Thread liangqi (D)

I can give some support from compass side. Also I'm recently working on opnfv 
installers' quickstart wrapper scripts( 
https://gerrit.opnfv.org/gerrit/#/c/36711/ ). Hope the scipts could ease 
developers/users better use the labaas resources.



Here are three questions, after checked the wiki page:

- How do the Laas resources allocated? Allocated as vpods pool and BM(1+3+2) 
pods pool?
- How do the vpods' and BM jumpserver's operating systems installed, manually 
pre installed by lab admin or auto installed trigger by jenkins when the pod is 
allocated?
- Do laas pods share the same jenkins master with other opnfv pods or the laas 
will host a jenkins master to manage all the laas resources?



Regards,
QiLiang


From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[opnfv-tech-discuss-boun...@lists.opnfv.org] on behalf of Luke Hinds 
[lhi...@redhat.com]
Sent: Monday, July 17, 2017 22:39
To: opnfv-tech-discuss
Subject: [opnfv-tech-discuss] Lab as a Service - Installer Support

Dear Installer Projects,

I have an action from the infra-wg to gauge which installers can support LaaS.

Please peruse the following wiki link for more details on the effort.

https://wiki.opnfv.org/display/INF/Lab+as+a+Service

Recommend you go over the work flow in detail, and consider if you have 
interfaces that can accept the requests and process deployment status.

Any question, please ask over this email or attend the infra-wg group.

Many Thanks,

Luke

--
Luke Hinds | NFV Partner Engineering | Office of Technology | Red Hat
e: lhi...@redhat.com | irc: lhinds @freenode | m: +44 
77 45 63 98 84 | t: +44 12 52 36 2483
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] SFC Project

2017-07-17 Thread andres . sanchez . ramos

Pavan,

I have not encountered those errors! It looks like there is already  
and SFC classifier already declared, but i thought that if you run the  
functest script it deleted anything that was previously declared.  
Maybe Manuel has any idea, i am still working on my scenario trying to  
set it up correctly.

Best regards,

Quoting "Pavan Gupta" :

HI Andres,
Thanks to your inputs, the test moved forward, though it failed.  
Here’s the log snippe. Let me know if you know how to fix this issue:

2017-07-17 12:24:16,434 - tacker_utils - ERROR - error  
[create_sfc(tacker_client, 'red', 'None', '['testVNF1',  
'testVNF2']')]: SFC with name red already exists!
2017-07-17 12:24:16,463 - tacker_utils - ERROR - error  
[create_sfc_classifier(tacker_client, 'red_http', 'None','red',  
'{'source_port': 0, 'protocol': 6, 'dest_port': 80}')]: 'SFC  
Classifier with name red_http already exists!’

2017-07-17 12:24:18,094 - ovs_logger - ERROR - list index out of range
2017-07-17 12:24:18,096 - sfc.lib.utils - INFO - This is the first_RSP:
2017-07-17 12:24:18,355 - ovs_logger - ERROR - list index out of range
2017-07-17 12:24:18,356 - sfc.lib.utils - INFO - These are the rsps: []
2017-07-17 12:24:19,435 - ovs_logger - ERROR - list index out of range
2017-07-17 12:24:19,437 - sfc.lib.utils - INFO - These are the rsps: []
2017-07-17 12:24:20,262 - sfc.lib.utils - INFO - Instance name and  
ip ta-8503-b3cf-4764-9894-f449e803e904-vdu1-ncexgzd3abmm:172.26.48.54
2017-07-17 12:24:20,263 - sfc.lib.utils - INFO - Waiting for  
instance  
ta-8503-b3cf-4764-9894-f449e803e904-vdu1-ncexgzd3abmm:172.26.48.54  
to come up

Pavan

On 17-Jul-2017, at 5:44 PM, andres.sanchez.ra...@estudiant.upc.edu wrote:

Hello Pavan,

I encountered a similar problem in my setting, it appears that the  
problem is that the configuration file is not updated with your  
installer IP address. So what i did was: edit the file  
"/home/opnfv/repos/sfc/sfc/tests/functest/config.yaml" and modify  
the installer IP address and cluster number. You can get the  
cluster number by executing the command "fuel node list" in your  
Fuel master machine.

I hope this helps you.

Best regards,

Quoting "Pavan Gupta" :

HI Andres,
I now hit issue related to 10.20.0.2 IP address. Though at time of  
starting the container I gave a different IP address, I see there  
are several files that have 10.20.0.2 IP address. Shouldn’t that  
change? This is where my script fails:

root@c8fc69ea9256:~# cat /home/opnfv/functest/results/sfc.log
2017-07-17 10:40:22,732 - SSH utils - ERROR - timed out
Traceback (most recent call last):
 File "./run_tests.py", line 189, in 
   main(report=args.report)
 File "./run_tests.py", line 81, in main
   installer_pwd=COMMON_CONFIG.installer_password)
 File  
"/home/opnfv/repos/releng/modules/opnfv/deployment/factory.py",  
line 43, in get_handler

   installer_pwd=installer_pwd)
 File  
"/home/opnfv/repos/releng/modules/opnfv/deployment/fuel/adapter.py", line  
26, in __init__

   pkey_file=None)
 File  
"/home/opnfv/repos/releng/modules/opnfv/deployment/manager.py",  
line 332, in __init__

   'Cannot establish connection to the installer node!')
Exception: Cannot establish connection to the installer node!

Pavan

On 13-Jul-2017, at 6:35 PM, andres.sanchez.ra...@estudiant.upc.edu wrote:

Hello Manuel | Pavan,

The error where 10.20.0.2 occurs afterwards (when executing  
functest testcase run odl-sfc), for what I can see this is  
ocurring at executing "functest env prepare".

If I understand correctly this error is indicating that the  
machine where you are executing the test does not have  
connectivity to Openstack admin endpoints (which are located in  
the admin network you set up in Fuel - 192.168.0.0/24 by  
default). So it is probably a networking configuration issue: you  
must be either on the same network as openstack admin endpoints  
(192.168.0.0) or your networking equipment must be able to route  
packets to this network. In my setup I did not have any problem  
with iptables so if you are using fuel this is probably not the  
issue.

Best regards,

Quoting "Manuel Buil" :

Andres, can you explain Pavan what you did to solve your issue? I think
he is also hitting the error you found that 10.20.0.2 is hardcoded.

Thanks,
Manuel

On Thu, 2017-07-13 at 15:28 +0530, Pavan Gupta wrote:

> Ok. Any idea what needs to be done. I am trying things at my

side.Pavan

> > > On 12-Jul-2017, at 7:32 PM, Manuel Buil  wrote:
> Hey Pavan,
>
> > > > > The container must be able to contact the openstack  
environment,

otherwise it cannot trigger openstack actions. Do you have perhaps
a problem with iptables?

>
> Regards,
> Manuel
> On Wed, 2017-07-12 at 19:05 +0530, Pavan Gupta wrote:
> > Hi Manuel,
> > > > > I have deployed the setup for SFC Functest now. However, while

preparing the environment, I see the following error:

> >
> >
> > >

Re: [opnfv-tech-discuss] SFC Project

2017-07-17 Thread Pavan Gupta

HI Andres,
Thanks to your inputs, the test moved forward, though it failed. Here’s the log 
snippe. Let me know if you know how to fix this issue:

2017-07-17 12:24:16,434 - tacker_utils - ERROR - error 
[create_sfc(tacker_client, 'red', 'None', '['testVNF1', 'testVNF2']')]: SFC 
with name red already exists!
2017-07-17 12:24:16,463 - tacker_utils - ERROR - error 
[create_sfc_classifier(tacker_client, 'red_http', 'None','red', 
'{'source_port': 0, 'protocol': 6, 'dest_port': 80}')]: 'SFC Classifier with 
name red_http already exists!’

2017-07-17 12:24:18,094 - ovs_logger - ERROR - list index out of range
2017-07-17 12:24:18,096 - sfc.lib.utils - INFO - This is the first_RSP:
2017-07-17 12:24:18,355 - ovs_logger - ERROR - list index out of range
2017-07-17 12:24:18,356 - sfc.lib.utils - INFO - These are the rsps: []
2017-07-17 12:24:19,435 - ovs_logger - ERROR - list index out of range
2017-07-17 12:24:19,437 - sfc.lib.utils - INFO - These are the rsps: []
2017-07-17 12:24:20,262 - sfc.lib.utils - INFO - Instance name and ip 
ta-8503-b3cf-4764-9894-f449e803e904-vdu1-ncexgzd3abmm:172.26.48.54
2017-07-17 12:24:20,263 - sfc.lib.utils - INFO - Waiting for instance 
ta-8503-b3cf-4764-9894-f449e803e904-vdu1-ncexgzd3abmm:172.26.48.54 to come up

Pavan

> On 17-Jul-2017, at 5:44 PM, andres.sanchez.ra...@estudiant.upc.edu wrote:
> 
> Hello Pavan,
> 
> I encountered a similar problem in my setting, it appears that the problem is 
> that the configuration file is not updated with your installer IP address. So 
> what i did was: edit the file 
> "/home/opnfv/repos/sfc/sfc/tests/functest/config.yaml" and modify the 
> installer IP address and cluster number. You can get the cluster number by 
> executing the command "fuel node list" in your Fuel master machine.
> 
> I hope this helps you.
> 
> Best regards,
> 
> Quoting "Pavan Gupta" :
> 
>> HI Andres,
>> I now hit issue related to 10.20.0.2 IP address. Though at time of starting 
>> the container I gave a different IP address, I see there are several files 
>> that have 10.20.0.2 IP address. Shouldn’t that change? This is where my 
>> script fails:
>> root@c8fc69ea9256:~# cat /home/opnfv/functest/results/sfc.log
>> 2017-07-17 10:40:22,732 - SSH utils - ERROR - timed out
>> Traceback (most recent call last):
>>  File "./run_tests.py", line 189, in 
>>main(report=args.report)
>>  File "./run_tests.py", line 81, in main
>>installer_pwd=COMMON_CONFIG.installer_password)
>>  File "/home/opnfv/repos/releng/modules/opnfv/deployment/factory.py", line 
>> 43, in get_handler
>>installer_pwd=installer_pwd)
>>  File "/home/opnfv/repos/releng/modules/opnfv/deployment/fuel/adapter.py", 
>> line 26, in __init__
>>pkey_file=None)
>>  File "/home/opnfv/repos/releng/modules/opnfv/deployment/manager.py", line 
>> 332, in __init__
>>'Cannot establish connection to the installer node!')
>> Exception: Cannot establish connection to the installer node!
>> 
>> Pavan
>> 
>>> On 13-Jul-2017, at 6:35 PM, andres.sanchez.ra...@estudiant.upc.edu wrote:
>>> 
>>> Hello Manuel | Pavan,
>>> 
>>> The error where 10.20.0.2 occurs afterwards (when executing functest 
>>> testcase run odl-sfc), for what I can see this is ocurring at executing 
>>> "functest env prepare".
>>> 
>>> If I understand correctly this error is indicating that the machine where 
>>> you are executing the test does not have connectivity to Openstack admin 
>>> endpoints (which are located in the admin network you set up in Fuel - 
>>> 192.168.0.0/24 by default). So it is probably a networking configuration 
>>> issue: you must be either on the same network as openstack admin endpoints 
>>> (192.168.0.0) or your networking equipment must be able to route packets to 
>>> this network. In my setup I did not have any problem with iptables so if 
>>> you are using fuel this is probably not the issue.
>>> 
>>> Best regards,
>>> 
>>> Quoting "Manuel Buil" :
>>> 
 Andres, can you explain Pavan what you did to solve your issue? I think
 he is also hitting the error you found that 10.20.0.2 is hardcoded.
 
 Thanks,
 Manuel
 
 
 On Thu, 2017-07-13 at 15:28 +0530, Pavan Gupta wrote:
> > Ok. Any idea what needs to be done. I am trying things at my
 side.Pavan
> 
> > > > On 12-Jul-2017, at 7:32 PM, Manuel Buil  wrote:
> > Hey Pavan,
> >
> > > > > > The container must be able to contact the openstack environment,
 otherwise it cannot trigger openstack actions. Do you have perhaps
 a problem with iptables?
> >
> > Regards,
> > Manuel
> > On Wed, 2017-07-12 at 19:05 +0530, Pavan Gupta wrote:
> > > Hi Manuel,
> > > > > > I have deployed the setup for SFC Functest now. However, while
 preparing the environment, I see the following error:
> > >
> > >
> > > > > > 2017-07-12 13:31:30,091 - prepare_env - INFO - >>Verifying
 connectivity to the admin endpoint

Re: [opnfv-tech-discuss] SFC Project

2017-07-17 Thread andres . sanchez . ramos

Hello Pavan,

I encountered a similar problem in my setting, it appears that the  
problem is that the configuration file is not updated with your  
installer IP address. So what i did was: edit the file  
"/home/opnfv/repos/sfc/sfc/tests/functest/config.yaml" and modify the  
installer IP address and cluster number. You can get the cluster  
number by executing the command "fuel node list" in your Fuel master  
machine.

I hope this helps you.

Best regards,

Quoting "Pavan Gupta" :

HI Andres,
I now hit issue related to 10.20.0.2 IP address. Though at time of  
starting the container I gave a different IP address, I see there  
are several files that have 10.20.0.2 IP address. Shouldn’t that  
change? This is where my script fails:

root@c8fc69ea9256:~# cat /home/opnfv/functest/results/sfc.log
2017-07-17 10:40:22,732 - SSH utils - ERROR - timed out
Traceback (most recent call last):
  File "./run_tests.py", line 189, in 
main(report=args.report)
  File "./run_tests.py", line 81, in main
installer_pwd=COMMON_CONFIG.installer_password)
  File  
"/home/opnfv/repos/releng/modules/opnfv/deployment/factory.py", line  
43, in get_handler

installer_pwd=installer_pwd)
  File  
"/home/opnfv/repos/releng/modules/opnfv/deployment/fuel/adapter.py",  
line 26, in __init__

pkey_file=None)
  File  
"/home/opnfv/repos/releng/modules/opnfv/deployment/manager.py", line  
332, in __init__

'Cannot establish connection to the installer node!')
Exception: Cannot establish connection to the installer node!

Pavan

On 13-Jul-2017, at 6:35 PM, andres.sanchez.ra...@estudiant.upc.edu wrote:

Hello Manuel | Pavan,

The error where 10.20.0.2 occurs afterwards (when executing  
functest testcase run odl-sfc), for what I can see this is ocurring  
at executing "functest env prepare".

If I understand correctly this error is indicating that the machine  
where you are executing the test does not have connectivity to  
Openstack admin endpoints (which are located in the admin network  
you set up in Fuel - 192.168.0.0/24 by default). So it is probably  
a networking configuration issue: you must be either on the same  
network as openstack admin endpoints (192.168.0.0) or your  
networking equipment must be able to route packets to this network.  
In my setup I did not have any problem with iptables so if you are  
using fuel this is probably not the issue.

Best regards,

Quoting "Manuel Buil" :

Andres, can you explain Pavan what you did to solve your issue? I think
he is also hitting the error you found that 10.20.0.2 is hardcoded.

Thanks,
Manuel

On Thu, 2017-07-13 at 15:28 +0530, Pavan Gupta wrote:

> Ok. Any idea what needs to be done. I am trying things at my

side.Pavan

> > > On 12-Jul-2017, at 7:32 PM, Manuel Buil  wrote:
> Hey Pavan,
>
> > > > > The container must be able to contact the openstack environment,

otherwise it cannot trigger openstack actions. Do you have perhaps
a problem with iptables?

>
> Regards,
> Manuel
> On Wed, 2017-07-12 at 19:05 +0530, Pavan Gupta wrote:
> > Hi Manuel,
> > > > > I have deployed the setup for SFC Functest now. However, while

preparing the environment, I see the following error:

> >
> >
> > > > > 2017-07-12 13:31:30,091 - prepare_env - INFO - >>Verifying

connectivity to the admin endpoint 192.168.0.2:35357...

> > > > > 2017-07-12 13:33:20,236 - prepare_env - ERROR - ERROR: Cannot

talk to the admin endpoint 192.168.0.2:35357 .

> > > > > 2017-07-12 13:33:20,236 - prepare_env - ERROR - Problem while

running 'check_os.sh'.
> > > > > > > > 2017-07-12 13:33:20,299 - functest_utils - ERROR  
- The command

'python /home/opnfv/repos/functest/functest/ci/prepare_env.py
start' failed.

> >
> >
> > > > > In case, you know if there is a fix for this issue,  
kindly let me

know.

> > Thanking you.
> > Regards,
> > Pavan
> >
> >
> > > > > > > On 11-Jul-2017, at 1:20 PM, Manuel Buil  
 wrote:

> > > Hello,
> > >
> > > > > > > Ok, if you are familiar with the fuel installer, then follow

this

> > > guide:
> > >
> > > > > > >  
https://wiki.opnfv.org/display/sfc/OPNFV-SFC+Functest+test+case

s

> > >
> > > Regards,
> > > Manuel
> > >
> > > On Mon, 2017-07-10 at 23:13 +0530, Pavan Gupta wrote:
> > > > Hi Manuel,
> > > > > > > > > Thank you for your reply. We are using Fuel installer to

create a

> > > > > > > > > setup within the company. In addition, we have access to

OPNFV

> > > > > > > > > community lab (Fuel Installer). I can try SFC in the

community lab if
> > > > > > > > > things are available. Kindly let me know what  
needs to be

done.

> > > > Pavan
> > > >
> > > > > > > > > > > > > > > > > On 10-Jul-2017, at 10:56 PM,  
Manuel Buil 

wrote:

> > > > >
> > > > > Hi Pavan,
> > > > >
> > > > > > > > > > > Yes, you can use OPNFV and the SFC project.  
When would you

like to
> > > > > > > > > > > deploy it? We are currently changing the  
platform and

moving

Re: [opnfv-tech-discuss] SFC Project

2017-07-17 Thread Pavan Gupta

HI Andres,
I now hit issue related to 10.20.0.2 IP address. Though at time of starting the 
container I gave a different IP address, I see there are several files that 
have 10.20.0.2 IP address. Shouldn’t that change? This is where my script fails:
root@c8fc69ea9256:~# cat /home/opnfv/functest/results/sfc.log
2017-07-17 10:40:22,732 - SSH utils - ERROR - timed out
Traceback (most recent call last):
  File "./run_tests.py", line 189, in 
main(report=args.report)
  File "./run_tests.py", line 81, in main
installer_pwd=COMMON_CONFIG.installer_password)
  File "/home/opnfv/repos/releng/modules/opnfv/deployment/factory.py", line 43, 
in get_handler
installer_pwd=installer_pwd)
  File "/home/opnfv/repos/releng/modules/opnfv/deployment/fuel/adapter.py", 
line 26, in __init__
pkey_file=None)
  File "/home/opnfv/repos/releng/modules/opnfv/deployment/manager.py", line 
332, in __init__
'Cannot establish connection to the installer node!')
Exception: Cannot establish connection to the installer node!

Pavan

> On 13-Jul-2017, at 6:35 PM, andres.sanchez.ra...@estudiant.upc.edu wrote:
> 
> Hello Manuel | Pavan,
> 
> The error where 10.20.0.2 occurs afterwards (when executing functest testcase 
> run odl-sfc), for what I can see this is ocurring at executing "functest env 
> prepare".
> 
> If I understand correctly this error is indicating that the machine where you 
> are executing the test does not have connectivity to Openstack admin 
> endpoints (which are located in the admin network you set up in Fuel - 
> 192.168.0.0/24 by default). So it is probably a networking configuration 
> issue: you must be either on the same network as openstack admin endpoints 
> (192.168.0.0) or your networking equipment must be able to route packets to 
> this network. In my setup I did not have any problem with iptables so if you 
> are using fuel this is probably not the issue.
> 
> Best regards,
> 
> Quoting "Manuel Buil" :
> 
>> Andres, can you explain Pavan what you did to solve your issue? I think
>> he is also hitting the error you found that 10.20.0.2 is hardcoded.
>> 
>> Thanks,
>> Manuel
>> 
>> 
>> On Thu, 2017-07-13 at 15:28 +0530, Pavan Gupta wrote:
>>> > Ok. Any idea what needs to be done. I am trying things at my
>> side.Pavan
>>> 
>>> > > > On 12-Jul-2017, at 7:32 PM, Manuel Buil  wrote:
>>> > Hey Pavan,
>>> >
>>> > > > > > The container must be able to contact the openstack environment,
>> otherwise it cannot trigger openstack actions. Do you have perhaps
>> a problem with iptables?
>>> >
>>> > Regards,
>>> > Manuel
>>> > On Wed, 2017-07-12 at 19:05 +0530, Pavan Gupta wrote:
>>> > > Hi Manuel,
>>> > > > > > I have deployed the setup for SFC Functest now. However, while
>> preparing the environment, I see the following error:
>>> > >
>>> > >
>>> > > > > > 2017-07-12 13:31:30,091 - prepare_env - INFO - >>Verifying
>> connectivity to the admin endpoint 192.168.0.2:35357...
>>> > > > > > 2017-07-12 13:33:20,236 - prepare_env - ERROR - ERROR: Cannot
>> talk to the admin endpoint 192.168.0.2:35357 .
>>> > > > > > 2017-07-12 13:33:20,236 - prepare_env - ERROR - Problem while
>> running 'check_os.sh'.
>>> > > > > > > > > 2017-07-12 13:33:20,299 - functest_utils - ERROR - The 
>>> > > > > > > > > command
>> 'python /home/opnfv/repos/functest/functest/ci/prepare_env.py
>> start' failed.
>>> > >
>>> > >
>>> > > > > > In case, you know if there is a fix for this issue, kindly let me
>> know.
>>> > > Thanking you.
>>> > > Regards,
>>> > > Pavan
>>> > >
>>> > >
>>> > > > > > > > On 11-Jul-2017, at 1:20 PM, Manuel Buil  
>>> > > > > > > > wrote:
>>> > > > Hello,
>>> > > >
>>> > > > > > > > Ok, if you are familiar with the fuel installer, then follow
>> this
>>> > > > guide:
>>> > > >
>>> > > > > > > > https://wiki.opnfv.org/display/sfc/OPNFV-SFC+Functest+test+case
>> s
>>> > > >
>>> > > > Regards,
>>> > > > Manuel
>>> > > >
>>> > > > On Mon, 2017-07-10 at 23:13 +0530, Pavan Gupta wrote:
>>> > > > > Hi Manuel,
>>> > > > > > > > > > Thank you for your reply. We are using Fuel installer to
>> create a
>>> > > > > > > > > > setup within the company. In addition, we have access to
>> OPNFV
>>> > > > > > > > > > community lab (Fuel Installer). I can try SFC in the
>> community lab if
>>> > > > > > > > > > things are available. Kindly let me know what needs to be
>> done.
>>> > > > > Pavan
>>> > > > >
>>> > > > > > > > > > > > > > > > > > On 10-Jul-2017, at 10:56 PM, Manuel Buil 
>>> > > > > > > > > > > > > > > > > > 
>> wrote:
>>> > > > > >
>>> > > > > > Hi Pavan,
>>> > > > > >
>>> > > > > > > > > > > > Yes, you can use OPNFV and the SFC project. When 
>>> > > > > > > > > > > > would you
>> like to
>>> > > > > > > > > > > > deploy it? We are currently changing the platform and
>> moving from
>>> > > > > > fuel
>>> > > > > > to openstack-ansible, however, we will not be ready before
>>> > > > > > September.
>>> > > > > >
>>> > > > > > Are you familiar with

[opnfv-tech-discuss] Lab as a Service - Installer Support

2017-07-17 Thread Luke Hinds

Dear Installer Projects,

I have an action from the infra-wg to gauge which installers can support
LaaS.

Please peruse the following wiki link for more details on the effort.

https://wiki.opnfv.org/display/INF/Lab+as+a+Service

Recommend you go over the work flow in detail, and consider if you have
interfaces that can accept the requests and process deployment status.

Any question, please ask over this email or attend the infra-wg group.

Many Thanks,

Luke

-- 
Luke Hinds | NFV Partner Engineering | Office of Technology | Red Hat
e: lhi...@redhat.com | irc: lhinds @freenode | m: +44 77 45 63 98 84 | t: +44
12 52 36 2483
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] 答复: [ha][availability] Progress on HA Guest APIs work

2017-07-17 Thread Fu Qiao

Hi, all. I send this email to check on the progress and see what we can achieve 
for the E release.

@Greg. How about the progress of the API work. Since the E release MS is 
approaching, I wonder what we can achieve for this release based on the 
progress we now have? Whether integration using compass is possible now?

@Kanglin & Qiujuan, how about the test case development work? I recall we had 
some discussion during the summit and you mentioned you are working on the HA 
test cases and have some plan for the E release. How is the progress?

Thank you!

 

发件人: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] 代表 Waines, Greg
发送时间: 2017年6月1日 20:38
收件人: opnfv-tech-discuss@lists.opnfv.org
主题: [opnfv-tech-discuss] [ha][availability] Progress on HA Guest APIs work

 

Just an FYI ... wrt Progress on HA Guest APIs work ...

 

Over the last week or so I have had some discussions on the [openstack-dev] 
[vitrage] [nova] mailing list,

discussing VM Heartbeat / Health-check Monitoring. 

· had the typical discussions of how it is this different than QEMU 
libvirt watchdog,

· had good suggestion to leverage the QEMU Guest Agent for the low 
level transport,

o 
https://wiki.libvirt.org/page/Qemu_guest_agent

o   which sets up the virtio serial device in QEMU and defines the basic 
transport layer for 
messaging between the host and guest, and

o   already has a NOVA flavor extraspec to enable this !



· I suggested that I not put this functionality in NOVA

o   since, at least implementation-wise, it is not coupled with NOVA,
i.e. I would have no NOVA changes now

o   NOVA doesn’t currently incorporate a lot of monitoring functionality,

o   AND personally I think it would be a much harder road to get the blueprint
accepted in NOVA

· I DID suggest that it be put in Vitrage

o   BUT (rightly) the Vitrage guys indicated that it was NOT really a fit for 
Vitrage, 
as Vitrage actually does no ‘monitoring’ itself ... it just provides 
‘datasource apis’
for external monitoring mechanisms, like Zabbix or Nagios or CollectD or ...

§  the Vitrage guys suggested contributing to Zabbix or Nagios

§  personally, would rather contribute directly to either openstack or opnfv
project, rather than to Zabbix or Nagios



· HOWEVER I did get interest from a couple of project leads from 
Masakari

o   Masakari == HA for VMs

o 
https://wiki.openstack.org/wiki/Masakari

o

 
https://specs.openstack.org/openstack/openstack-user-stories/user-stories/proposed/ha_vm.html

o   they are NOT under BIG TENT right now, but are submitting for this this year

o   they do

§  host, process and instance monitoring, and

§  internal auto-recovery of VMs ß I realize this is contrary to OPNFV / 
MANO philosophy, but it is OPTIONAL/CONFIGURABLE

o   they are introducing alternate reporting APIs on the backend of the 
monitoring functions

§  e.g. their default is to the internal Masakari API which then drives their 
auto-recovery engine

§  they are integrating with reporting monitoring results to Mistral, and

§  they seem open to integrating with reporting monitoring results to Vitrage

othey seem interested in the VM Heartbeat / Health-check Monitoring

§  they only do black-box / non-intrusive type instance monitoring today

§  agree that this would expand their scope

§  but see value in it

o   They were willing to accept a blueprint on VM HB/HC Monitoring

· I have submitted the blueprint and spec file to the Masakari 
Launchpad:
Blueprint:  
https://blueprints.launchpad.net/masakari/+spec/intrusive-instance-monitoring
Spec: https://review.openstack.org/#/c/469070/

 

 

Greg.

 

 

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [OPNFV Helpdesk #43045] RE: [barometer] I would like to contribute to the PROJECT

2017-07-17 Thread maryam.tah...@intel.com via RT

Thank you

> -Original Message-
> From: Trevor Bramwell via RT [mailto:opnfv-helpd...@rt.linuxfoundation.org]
> Sent: Friday, July 14, 2017 8:59 PM
> To: Tahhan, Maryam 
> Cc: Foley, Emma L ; opnfv-tech-
> disc...@lists.opnfv.org
> Subject: [OPNFV Helpdesk #43045] RE: [opnfv-tech-discuss] [barometer] I would
> like to contribute to the PROJECT
> 
> Hi Maryam,
> 
> I've sent an invite to Emma.
> 
> Hi Emma,
> 
> I have sent you an invite to join the Barometer contributors group. This will
> prompt you to create a Linux Foundation account if you don't already have one.
> Please choose a username without spaces or special characters as Gerrit
> requires a valid unix username. You will also need to sign the individual 
> CLA[1]
> and upload an ssh key in Gerrit[2] before you can push code.
> 
> Don't hesitate to get in touch (helpd...@opnfv.org) if you have any further
> questions.
> 
> Welcome to OPNFV and thanks for contributing to barometer!
> 
> Regards,
> Trevor Bramwell
> 
> [1] https://gerrit.opnfv.org/gerrit/#/settings/agreements
> [2] https://gerrit.opnfv.org/gerrit/#/settings/ssh-keys
> 
> On Fri Jul 14 03:57:29 2017, maryam.tah...@intel.com wrote:
> > Hi Aric
> > Can you please give Emma Permissions to contribute to barometer?
> >
> > Thanks
> >  Maryam
> >
> > > -Original Message-
> > > From: opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:opnfv-tech-
> > > discuss-
> > > boun...@lists.opnfv.org] On Behalf Of Foley, Emma L
> > > Sent: Friday, July 14, 2017 10:55 AM
> > > To: opnfv-tech-discuss@lists.opnfv.org
> > > Subject: [opnfv-tech-discuss] [barometer] I would like to contribute
> > > to the PROJECT
> > >
> > >
> > > ___
> > > opnfv-tech-discuss mailing list
> > > opnfv-tech-discuss@lists.opnfv.org
> > > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
> 
> 


___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] Topics for this week's Technical Community call

[opnfv-tech-discuss] [release][danube] OPNFV Danube 3.0 has been released

Re: [opnfv-tech-discuss] Lab as a Service - Installer Support

Re: [opnfv-tech-discuss] Lab as a Service - Installer Support

Re: [opnfv-tech-discuss] SFC Project

Re: [opnfv-tech-discuss] SFC Project

Re: [opnfv-tech-discuss] SFC Project

Re: [opnfv-tech-discuss] SFC Project

[opnfv-tech-discuss] Lab as a Service - Installer Support

[opnfv-tech-discuss] 答复: [ha][availability] Progress on HA Guest APIs work

Re: [opnfv-tech-discuss] [OPNFV Helpdesk #43045] RE: [barometer] I would like to contribute to the PROJECT

11 matches

Site Navigation

Mail list logo

Footer information