date:20170730

Re: [opnfv-tech-discuss] Error fuel deployment in all versions

2017-07-30 Thread Michael Polenchuk

Hi,

Could you please get the latest Fuel Danube iso?
Also please check out the disk free space on fuel master.

On Tue, Jul 25, 2017 at 10:26 PM, Ishpreet Kaur  wrote:

>
> Hi team,
>>
>> As in earlier message i told you about an error during fuel(brahmputra)
>> version , but today i try to deploy colorado1.0 version and getting the
>> same error at provisiong
>>
>> i am enclosing the error report, i hope you can help me please, as it is
>> a last of my deployment please
>> i shall be really thankful to you.
>>
>>
>> here an error during provisioning of nodes:
>>
>> Provision has failed. Failed to execute hook 'shell' Failed to run
>> command cd / && fa_build_image --image_build_dir /var/lib/fuel/ibp
>> --log-file /var/log/fuel-agent-env-2.log --data_driver nailgun_build_image
>> --input_data '{"image_data": {"/boot": {"container": "gzip", "uri": "
>> http://10.20.0.2:8080/targetimages/env_2_ubuntu_1404_amd64-boot.img.gz;,
>> "format": "ext2"}, "/": {"container": "gzip", "uri": "
>> http://10.20.0.2:8080/targetimages/env_2_ubuntu_1404_amd64.img.gz;,
>> "format": "ext4"}}, "output": "/var/www/nailgun/targetimages", "repos":
>> [{"name": "ubuntu", "section": "main multiverse restricted universe",
>> "uri": "http://10.20.0.2:8080/mirrors/ubuntu;, "priority": null,
>> "suite": "trusty", "type": "deb"}, {"name": "ubuntu-updates", "section":
>> "main multiverse restricted universe", "uri": "http://10.20.0.2:8080/
>> mirrors/ubuntu", "priority": null, "suite": "trusty-updates", "type":
>> "deb"}, {"name": "ubuntu-security", "section": "main multiverse restricted
>> universe", "uri": "http://10.20.0.2:8080/mirrors/ubuntu;, "priority":
>> null, "suite": "trusty-security", "type": "deb"}], "packages": ["acl",
>> "anacron", "bash-completion", "bridge-utils", "bsdmainutils",
>> "build-essential", "cloud-init", "curl", "daemonize", "debconf-utils",
>> "gdisk", "grub-pc", "hpsa-dkms", "hwloc", "i40e-dkms", "linux-firmware",
>> "linux-firmware-nonfree", "linux-headers-generic-lts-trusty",
>> "linux-image-generic-lts-trusty", "lvm2", "mcollective", "mdadm",
>> "multipath-tools", "multipath-tools-boot", "nailgun-agent",
>> "nailgun-mcagents", "network-checker", "ntp", "openssh-client",
>> "openssh-server", "puppet", "python-amqp", "ruby-augeas", "ruby-ipaddress",
>> "ruby-json", "ruby-netaddr", "ruby-openstack", "ruby-shadow", "ruby-stomp",
>> "telnet", "ubuntu-minimal", "ubuntu-standard", "uuid-runtime", "vim",
>> "virt-what", "vlan"], "codename": "trusty"}' (node master returned 255).
>>
>>
>> I will really appreciate if anyone can help me.
>>
>> Regards
>> Ishpreet kaur
>> Uottawa
>>
>
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>
>


-- 
  Michael Polenchuk
  Private Cloud / Mirantis Inc.
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [dovetail] Request for a slot in tomorrow's weekly call

2017-07-30 Thread Zenghui Shi

Hi Srikanth & Tim,

Thanks for sharing the findings on test gaps in weekly dovetail meeting!
Is it possible the slides can be shared so that anyone who's interested in
can get to understand and follow-up on some of the test items?

Regards,
zenghui


On Thu, Jul 27, 2017 at 11:18 PM, Srikanth Vavilapalli <
srikanth.vavilapa...@ericsson.com> wrote:

> Hi
>
>
>
> In tomorrow’s weekly call, Tim and myself (from Ericsson) wanted to share
> our findings on test gaps in basic cloud capability, security and High
> availability areas.
>
>
>
> Can you plz add to the agenda if we can get some time for this?
>
>
>
> Thanks
>
> Srikanth
>
>
>
>
>
>
>
> ___
> 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] 答复: Reply: Reply: [availability]High Availability Project meeting on Jul. 26

2017-07-30 Thread Fu Qiao

Hi, Kanglin. Thank you for sharing this work. I find this very interesting
and useful. The diagram on the 4th page means a lot to us, since it helps us
to make sure the HA relationship of all these multiple component in NFV
scenarios.

Do you think if it is possible to submit a document about this work in the
HA project to help illustrate this goal oriented framework? I think it will
be meaningful to the whole community and to other HA analysis group, such as
ETSI, and lots of work can be developed based on this work.

 

 

发件人: Tony Yin [mailto:14_...@tongji.edu.cn] 
发送时间: 2017年7月28日 16:20
收件人: 'Fu Qiao' ; 'juan_qiu' ; 'Jolliffe, Ian' ; 'Waines, Greg'
; 'Stefan Arntzen' ;
'Yue Yuan' ; opnfv-tech-discuss@lists.opnfv.org
主题: Reply: Reply: [opnfv-tech-discuss][availability]High Availability
Project meeting on Jul. 26

 

Hi all, I got the permission of my supervisor, so here is my slide of my
academic work shared on Wednesday.

 

BRs,

Kanglin

 

发件人: Fu Qiao [mailto:fuq...@chinamobile.com] 
发送时间: 2017年7月27日 9:36
收件人: 'Tony Yin'; 'juan_qiu'; 'Jolliffe, Ian'; 'Waines, Greg'; 'Stefan
Arntzen'; 'Yue Yuan'; opnfv-tech-discuss@lists.opnfv.org
 
主题: 答复: Reply: [opnfv-tech-discuss][availability]High Availability
Project meeting on Jul. 26

 

Hi, all. Below are the minutes for yesterday’s call. Thank you for the
discussion.

 

Minutes

1, Greg updates the progress of BP for masakari. The BPs have been accepted
a few weeks ago, and code development work has began. We are now targeting Q
release of openstack. We plan to integrate the API work into installers of
OPNFV after this is integrated in OpenStack releases. Therefore the work may
wait till next year.

2, Kanglin introduces the HA testcases for E release. 3 testcases are
included, which are TC for pacemaker, rabbitMQ, and virtual router. 

3, Kanglin introduces his acedemic work, which is a map of HA analysis of
NFV. This map will help us locate the failure of NFV and the recovery
mechenism, which testcase is missing for HA, and also help us better explain
the HA requirement. 

 

 

发件人: Tony Yin [mailto:14_...@tongji.edu.cn] 
发送时间: 2017年7月24日 17:51
收件人: 'Fu Qiao'  >;
'juan_qiu'  >;
'Jolliffe, Ian'  >; 'Waines, Greg'
 >; 'Stefan
Arntzen'  >;
'Yue Yuan'  >;
opnfv-tech-discuss@lists.opnfv.org
 
主题: Reply: [opnfv-tech-discuss][availability]High Availability Project
meeting on Jul. 26

 

Hi all,

 

I’ve finished the documents drafts of HA test cases for E release on
etherpad:

 

https://etherpad.opnfv.org/p/yardstick_ha_tc013   OpenStack Controller
Messaging Queue Service High Availability

https://etherpad.opnfv.org/p/yardstick_ha_tc014   OpenStack Controller
Cluster Management Service High Availability

https://etherpad.opnfv.org/p/yardstick_ha_tc015   OpenStack Controller
Virtual Router Service High Availability

 

Feel free to give comments on them. J

 

Kanglin

 

发件人: Fu Qiao [mailto:fuq...@chinamobile.com] 
发送时间: 2017年7月19日 10:06
收件人: 'Yin Tony'; 'juan_qiu'; 'Jolliffe, Ian'; 'Waines, Greg'; 'Stefan
Arntzen'; 'Yue Yuan'; opnfv-tech-discuss@lists.opnfv.org
 
主题: [opnfv-tech-discuss][availability]High Availability Project meeting on
Jul. 26

 


Hi, all. Below are the agenda for our next project call on Jul. 26, at
6am(PST). Kanglin will introduce the HA test cases added for E release.


@Greg, would you please also give some updates on the HA API BP?


Thank you and hope to talk to you all.


 


Next Meeting on 13:00-14:00 UTC, Wednesday, Jul. 26


https://global.gotomeeting.com/join/391235029

 

Toll free NO.

USA: +1 (571) 317-3116

 

Meeting ID: 391-235-029


Agenda:


HA test case plan for E release �C Kanglin

 

 

 

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

Re: [opnfv-tech-discuss] [Doctor] Integration with VNFM

2017-07-30 Thread Afek, Ifat (Nokia - IL/Kfar Sava)

Hi,

Two corrections:


· In vitrage.conf, it should be ‘notifiers’ and not ‘Notifiers’:

[DEFAULT]

notifiers = nova


· In order to make the Nova notifier call Nova force-down API you 
should add a mark_down action in one of Vitrage templates. You can see an 
example in the template sample: 
https://github.com/openstack/vitrage/blob/master/etc/vitrage/templates.sample/host_down_scenarios.yaml

For additional explanations: 
https://docs.openstack.org/vitrage/latest/contributor/vitrage-template-format.html

Best Regards,
Ifat.

From:  on behalf of "Afek, Ifat 
(Nokia - IL/Kfar Sava)" 
Date: Sunday, 30 July 2017 at 10:16
To: Ciprian Barbu 
Cc: "opnfv-tech-discuss@lists.opnfv.org" 
Subject: Suspected SPAM - Re: [opnfv-tech-discuss] [Doctor] Integration with 
VNFM

Hi Ciprian,

You understood correctly. The call to Nova API is done by the Vitrage Nova 
notifier, if it is enabled. To enable it add you /etc/vitrage/vitrage.conf:

[DEFAULT]
Notifiers = nova

Best Regards,
Ifat.


From: Ciprian Barbu 
Date: Friday, 28 July 2017 at 13:34
To: "Afek, Ifat (Nokia - IL/Kfar Sava)" 
Cc: "opnfv-tech-discuss@lists.opnfv.org" , 
Paul Vaduva , Cristina Pauna , 
Ryota Mibu 
Subject: RE: [opnfv-tech-discuss] [Doctor] Integration with VNFM

Hello Ifat,

Since we started talking about Vitrage, we are trying to understand how the 
doctor integration works, for the mark_host_down event. My understanding was 
that Vitrage will issue the mark host down API in Nova which should trigger an 
event/alarm in Aodh, but it’s not obvious from the source code. Is this how it 
works?

Thank you and regards,
/Ciprian

From: Afek, Ifat (Nokia - IL/Kfar Sava) [mailto:ifat.a...@nokia.com]
Sent: Monday, July 24, 2017 8:04 PM
To: Ciprian Barbu 
Cc: opnfv-tech-discuss@lists.opnfv.org; Ryota Mibu 
Subject: Re: [opnfv-tech-discuss] [Doctor] Integration with VNFM

Sounds great, we’ll be happy to see it pushed ☺

Best Regards,
Ifat.

From: Ciprian Barbu >
Date: Monday, 24 July 2017 at 19:37
To: "Afek, Ifat (Nokia - IL/Kfar Sava)" 
>
Cc: 
"opnfv-tech-discuss@lists.opnfv.org" 
>,
 Ryota Mibu >
Subject: RE: [opnfv-tech-discuss] [Doctor] Integration with VNFM

Hi,

For Vitrage we actually started a Fuel plugin, it hasn’t been pushed upstream 
yet, mainly because Fuel is being replaced with MCP. It’s a rather simple 
plugin but it seems to do the job. We are interested in making it work with 
Doctor and Tacker for the moment, but we are still experimenting with it. Being 
integrated with Zabbix also looked good at the time.

Thanks and regards,
/Ciprian

From: Afek, Ifat (Nokia - IL/Kfar Sava) [mailto:ifat.a...@nokia.com]
Sent: Monday, July 24, 2017 7:27 PM
To: Ciprian Barbu >
Cc: 
opnfv-tech-discuss@lists.opnfv.org; 
Ryota Mibu >
Subject: Re: [opnfv-tech-discuss] [Doctor] Integration with VNFM

Hi Ciprian,

As Ryota stated, Vitrage is not officially recognized as a Doctor Inspector 
implementation, mainly because it is not supported in any of the OPNFV 
installers yet.
I assume that you manually installed Vitrage on top of the Fuel deployment?

Vitrage is able to respond to the Doctor monitor compute.host.down event and 
call Nova force-down API. In addition, it gets topology and alarm information 
from other datasources including OpenStack components, Zabbix, Nagios, 
Collectd, etc. The combination of Vitrage and Zabbix is already used in 
production in several environments. Vitrage can send notifications to external 
components, like send SNMP traps, execute Mistral workflows or send HTTP 
notifications (in progress). You can find more information in the Vitrage wiki 
page[1] and OpenStack documentation[2].

[1] https://wiki.openstack.org/wiki/Vitrage
[2] https://docs.openstack.org/vitrage/latest/

Best Regards,
Ifat.


From: 
>
 on behalf of Ryota Mibu >
Date: Monday, 24 July 2017 at 18:19
To: Ciprian Barbu >
Cc: 
"opnfv-tech-discuss@lists.opnfv.org" 
>
Subject: Re: [opnfv-tech-discuss] [Doctor]

Re: [opnfv-tech-discuss] [Doctor] Integration with VNFM

2017-07-30 Thread Afek, Ifat (Nokia - IL/Kfar Sava)

Hi Ciprian,

You understood correctly. The call to Nova API is done by the Vitrage Nova 
notifier, if it is enabled. To enable it add you /etc/vitrage/vitrage.conf:

[DEFAULT]
Notifiers = nova

Best Regards,
Ifat.


From: Ciprian Barbu 
Date: Friday, 28 July 2017 at 13:34
To: "Afek, Ifat (Nokia - IL/Kfar Sava)" 
Cc: "opnfv-tech-discuss@lists.opnfv.org" , 
Paul Vaduva , Cristina Pauna , 
Ryota Mibu 
Subject: RE: [opnfv-tech-discuss] [Doctor] Integration with VNFM

Hello Ifat,

Since we started talking about Vitrage, we are trying to understand how the 
doctor integration works, for the mark_host_down event. My understanding was 
that Vitrage will issue the mark host down API in Nova which should trigger an 
event/alarm in Aodh, but it’s not obvious from the source code. Is this how it 
works?

Thank you and regards,
/Ciprian

From: Afek, Ifat (Nokia - IL/Kfar Sava) [mailto:ifat.a...@nokia.com]
Sent: Monday, July 24, 2017 8:04 PM
To: Ciprian Barbu 
Cc: opnfv-tech-discuss@lists.opnfv.org; Ryota Mibu 
Subject: Re: [opnfv-tech-discuss] [Doctor] Integration with VNFM

Sounds great, we’ll be happy to see it pushed ☺

Best Regards,
Ifat.

From: Ciprian Barbu >
Date: Monday, 24 July 2017 at 19:37
To: "Afek, Ifat (Nokia - IL/Kfar Sava)" 
>
Cc: 
"opnfv-tech-discuss@lists.opnfv.org" 
>,
 Ryota Mibu >
Subject: RE: [opnfv-tech-discuss] [Doctor] Integration with VNFM

Hi,

For Vitrage we actually started a Fuel plugin, it hasn’t been pushed upstream 
yet, mainly because Fuel is being replaced with MCP. It’s a rather simple 
plugin but it seems to do the job. We are interested in making it work with 
Doctor and Tacker for the moment, but we are still experimenting with it. Being 
integrated with Zabbix also looked good at the time.

Thanks and regards,
/Ciprian

From: Afek, Ifat (Nokia - IL/Kfar Sava) [mailto:ifat.a...@nokia.com]
Sent: Monday, July 24, 2017 7:27 PM
To: Ciprian Barbu >
Cc: 
opnfv-tech-discuss@lists.opnfv.org; 
Ryota Mibu >
Subject: Re: [opnfv-tech-discuss] [Doctor] Integration with VNFM

Hi Ciprian,

As Ryota stated, Vitrage is not officially recognized as a Doctor Inspector 
implementation, mainly because it is not supported in any of the OPNFV 
installers yet.
I assume that you manually installed Vitrage on top of the Fuel deployment?

Vitrage is able to respond to the Doctor monitor compute.host.down event and 
call Nova force-down API. In addition, it gets topology and alarm information 
from other datasources including OpenStack components, Zabbix, Nagios, 
Collectd, etc. The combination of Vitrage and Zabbix is already used in 
production in several environments. Vitrage can send notifications to external 
components, like send SNMP traps, execute Mistral workflows or send HTTP 
notifications (in progress). You can find more information in the Vitrage wiki 
page[1] and OpenStack documentation[2].

[1] https://wiki.openstack.org/wiki/Vitrage
[2] https://docs.openstack.org/vitrage/latest/

Best Regards,
Ifat.


From: 
>
 on behalf of Ryota Mibu >
Date: Monday, 24 July 2017 at 18:19
To: Ciprian Barbu >
Cc: 
"opnfv-tech-discuss@lists.opnfv.org" 
>
Subject: Re: [opnfv-tech-discuss] [Doctor] Integration with VNFM

Hi Ciprian,


Thank you for checking out Doctor project and reaching out us.

In Danube, we officially support OpenStack Congress, but haven’t supported 
Vitrage yet. See, our release notes [1]. I’m not a fuel expert, but doctor 
driver in Congress may not be enabled in default, as it is not in the default 
driver list to be loaded in upstream codebase. but it is available with proper 
Congress configuration. Otherwise, the driver code was omitted from the 
original Congress code in fuel plugin. Such situation couldn’t happen normally. 
Regarding Vitrage, I know they have doctor driver and you can check out [2].

We found there is polling mechanism in Zabbix, that is potentially make a delay 
in passing fault notification to Consumers. Due to that observation, we are not 
pushing Zabbix as typical Doctor Component so far, although it sometimes makes 
sense when you see benefits

Re: [opnfv-tech-discuss] Error fuel deployment in all versions

Re: [opnfv-tech-discuss] [dovetail] Request for a slot in tomorrow's weekly call

[opnfv-tech-discuss] 答复: Reply: Reply: [availability]High Availability Project meeting on Jul. 26

Re: [opnfv-tech-discuss] [Doctor] Integration with VNFM

Re: [opnfv-tech-discuss] [Doctor] Integration with VNFM

5 matches

Site Navigation

Mail list logo

Footer information