<div dir="auto"><div dir="ltr">Dear Ifat,<div><br></div><div>Usman is here. Previously, I contacted you for contributing to OpenStack Vitrage project but could not follow up with you for sometime due to various reasons.</div><div><br></div><div>However, to get actively involved in OpenStack project, I have decided to join OpenStack Summit in Sydney.</div><div><br></div><div>Also, based on my previous experience withe Vitrage project that is already in shape, so its not easy to propose new ideas. </div><div><br></div><div>Therefore, a better way to start contributing to development side with already proposed and on-going development.</div></div></div><div class="gmail_extra"><br clear="all"><div><div class="m_2426927164473325861gmail_signature" data-smartmail="gmail_signature"><div style="text-align:left">-- <br></div><font style="FONT-FAMILY:trebuchet ms,sans-serif" size="2"><b style="COLOR:rgb(51,102,255)"><br>Regards</b></font><br>
<div style="TEXT-ALIGN:left;MARGIN-LEFT:40px"><b><br><span style="FONT-FAMILY:comic sans ms,sans-serif">Muhammad Usman</span></b><span style="FONT-FAMILY:comic sans ms,sans-serif"> </span><br style="FONT-FAMILY:comic sans ms,sans-serif"><span style="FONT-FAMILY:comic sans ms,sans-serif">Application Engineer</span><br style="FONT-FAMILY:comic sans ms,sans-serif"><span style="FONT-FAMILY:comic sans ms,sans-serif"><font color="#000099">LMK Resources (pvt) Limited</font><br><a href="http://www.lmkr.com/" target="_blank">www.lmkr.com</a> <br style="FONT-FAMILY:comic sans ms,sans-serif"></span><span style="FONT-FAMILY:comic sans ms,sans-serif">+92 (323) 5599
068</span><b><br></b></div></div></div>
<br><div class="gmail_quote">On Mon, Mar 27, 2017 at 7:32 PM, Afek, Ifat (Nokia - IL/Kfar Sava) <span dir="ltr"><<a href="mailto:ifat.afek@nokia.com" target="_blank">ifat.afek@nokia.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
Let me try and explain the more general use case.<br>
<br>
You can query OVS for the switches information, and understand how they are mapped to one another. This is not enough for knowing the exact route of the network traffic for a certain VM.<br>
<br>
A certain switch can be connected to more than one other switch. You can, as you said, query the network type (encapsulation) information from Neutron. But then you will need in addition to query the rules of the specific switch from OVS, in order to know which route to take for each encapsulation type.<br>
<br>
Another problematic use case is when the switches are not connected to each other. The traffic can be redirected by a network-stack software component, so you will have to query it in addition in order to tell the route.<br>
<br>
And on top of all this, we need to think how to best represent this information in Vitrage (i.e. how to draw the graph, which vertices to connect to one another, etc.).<br>
<br>
IMO, this is all feasible and will give a lot of value to Vitrage. Just not easy to implement.<br>
<br>
Best Regards,<br>
Ifat.<br>
<div><div class="m_2426927164473325861h5"><br>
<br>
On 22/03/2017, 08:50, "Muhammad Usman" <<a href="mailto:usman476@gmail.com" target="_blank">usman476@gmail.com</a>> wrote:<br>
<br>
Hello Ifat,<br>
<br>
I tried to see more in depth about the issues you mentioned regarding<br>
the extension of vSwitches. Due to a lot of complexity involved in<br>
generating this topology and associated effects, I believe we need to<br>
setup some baseline (e.g. adding a configuration file for specifying<br>
bridges in existing deployment setup). Then using that baseline,<br>
topology can be constructed as well as type of network can be<br>
extracted from neutron and associated path followed (e.g. vlan or<br>
vxlan). However, more general case you mentioned, I cannot get it. Do<br>
you mean nova-network?<br>
<br>
Regarding the sunburst representation - Yes I agree, if you want to<br>
keep compute hierarchy separate then addition of networking components<br>
is not a good idea.<br>
<br>
Also, suggestions from other vitrage members are welcomed.<br>
<br>
<br>
> On Thu, Mar 16, 2017 at 6:44 PM, Afek, Ifat (Nokia - IL) <<br>
> <a href="mailto:ifat.afek@nokia.com" target="_blank">ifat.afek@nokia.com</a> <javascript:;>> wrote:<br>
><br>
>> Hi,<br>
>><br>
>><br>
>><br>
>> Adding switches to the Vitrage topology is generally a good idea, but the<br>
>> implementation might be very complex. Your diagram shows a simple use<br>
> case,<br>
>> where all switches are linked to one another and it is easy to determine<br>
>> the effect of a failure on the vms. However, in the more general case<br>
> there<br>
>> might be switches without a connecting port (e.g. they might be connected<br>
>> via the network stack). In such cases, it is not clear how to model the<br>
>> switches topology in Vitrage. Another case to consider is when the<br>
>> network<br>
>> type affects the packets path, like vlan vs. vxlan. If you have an idea<br>
>> of<br>
>> how to solve these issues, I will be happy to hear it.<br>
>><br>
>><br>
>><br>
>> Regarding the sunburst representation – I’m not sure I understand your<br>
>> diagram. Currently the sunburst is meant to show (only) the compute<br>
>> hierarchy: zones, hosts and instances. It is arranged in a containment<br>
>> relationship, i.e. every instance on the outer ring appears next to its<br>
>> host in the inner ring. If you add the bridges in the middle, you lose<br>
> this<br>
>> containment relationship. Can you please explain to me the suggested<br>
>> diagram?<br>
>><br>
>><br>
>><br>
>> BTW, you can send such questions to OpenStack mailing list (<br>
>> <a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.<wbr>org</a> <javascript:;>) with [vitrage] tag in<br>
> the title, and<br>
>> possibly get replies from other contributors as well.<br>
>><br>
>><br>
>><br>
>> Best Regards,<br>
>><br>
>> Ifat.<br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> *From: *Muhammad Usman <<a href="mailto:usman@smartx.kr" target="_blank">usman@smartx.kr</a> <javascript:;>><br>
>> *Date: *Monday, 13 March 2017 at 09:16<br>
>><br>
>> *To: *"Afek, Ifat (Nokia - IL)" <<a href="mailto:ifat.afek@nokia.com" target="_blank">ifat.afek@nokia.com</a> <javascript:;>><br>
>> *Cc: *JungSu Han <<a href="mailto:jshan@smartx.kr" target="_blank">jshan@smartx.kr</a> <javascript:;>><br>
>> *Subject: *Re: OpenStack Vitrage<br>
>><br>
>><br>
>><br>
>> Hi Ifat,<br>
>><br>
>> I attached our idea of extending the Vitrage Topology to include Virtual<br>
>> switches.<br>
>><br>
>> The reason, I mentioned about adding switches part in Vitrage is because<br>
>> we experienced looping issues that effect all infrastructure resources<br>
>> (i.e. physical host as well as vm's) performance. Therefore, it's<br>
> important<br>
>> to monitor the virtual switches as well to assist overall monitoring/RCA<br>
>> tasks.<br>
>><br>
>> I think this idea will extend the Vitrage scope to touch some portion of<br>
>> SDN (e.g. if we consider the SDN managed virtual switches) as well.<br>
>><br>
>><br>
>><br>
>> On Thu, Mar 9, 2017 at 6:49 PM, Muhammad Usman <<a href="mailto:usman@smartx.kr" target="_blank">usman@smartx.kr</a><br>
> <javascript:;>> wrote:<br>
>><br>
>> Dear Ifat,<br>
>><br>
>> Thanks for your guidance, I managed to install Vitrage properly using<br>
>> Master branches for both OpenStack and Vitrage.<br>
>><br>
>> Now, I will look into the visualization as well as other aspects.<br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> On Thu, Mar 9, 2017 at 2:43 PM, Afek, Ifat (Nokia - IL) <<br>
>> <a href="mailto:ifat.afek@nokia.com" target="_blank">ifat.afek@nokia.com</a> <javascript:;>> wrote:<br>
>><br>
>> Hi,<br>
>><br>
>><br>
>><br>
>> I have also noticed this problem, that Vitrage Ocata is not compatible<br>
>> with Horizon Newton.<br>
>><br>
>> If you just want an OpenStack working, you should use a stable version.<br>
>> Stable/Ocata is the newest one (just released a few weeks ago). On the<br>
>> other hand, if you want to contribute code, you better take the master<br>
>> branch. Alternatively, you can take stable/ocata for all projects, and<br>
>> the<br>
>> master for Vitrage. This should work (for now, since Pike has just<br>
> started).<br>
>><br>
>><br>
>><br>
>> Best Regards,<br>
>><br>
>> Ifat.<br>
>><br>
>><br>
>><br>
>> *From: *Muhammad Usman <<a href="mailto:usman@smartx.kr" target="_blank">usman@smartx.kr</a> <javascript:;>><br>
>> *Date: *Wednesday, 8 March 2017 at 15:21<br>
>><br>
>><br>
>> *To: *"Afek, Ifat (Nokia - IL)" <<a href="mailto:ifat.afek@nokia.com" target="_blank">ifat.afek@nokia.com</a> <javascript:;>><br>
>> *Cc: *JungSu Han <<a href="mailto:jshan@smartx.kr" target="_blank">jshan@smartx.kr</a> <javascript:;>><br>
>> *Subject: *Re: OpenStack Vitrage<br>
>><br>
>><br>
>><br>
>> Ifat,<br>
>><br>
>> after adding the mentioned line in /etc/heat/policy.json first error "You<br>
>> are not authorized to use global_index" seems to be solved.<br>
>><br>
>> However, in Horizon I still see same error (file is attached).<br>
>><br>
>> So, After looking inside the code I found that I installed OpenStack<br>
>> using<br>
>> stable/newton branch but Vitrage is installed from Master branch. Since,<br>
>> there are few changes in code (python-vitrageclient/<br>
> vitrageclient/client.py)<br>
>> that's why I think this error is occurring. Therefore, I will try to fix<br>
>> this problem by using same branch (i.e. stable/newton).<br>
>><br>
>><br>
>><br>
>> On Wed, Mar 8, 2017 at 9:08 PM, Afek, Ifat (Nokia - IL) <<br>
>> <a href="mailto:ifat.afek@nokia.com" target="_blank">ifat.afek@nokia.com</a> <javascript:;>> wrote:<br>
>><br>
>> Hi,<br>
>><br>
>><br>
>><br>
>> Try to edit /etc/heat/policy.json:<br>
>><br>
>><br>
>><br>
>> "stacks:global_index": "rule:deny_stack_user",<br>
>><br>
>><br>
>><br>
>> Then restart vitrage-graph.<br>
>><br>
>><br>
>><br>
>> Let me know if it solves the problem,<br>
>><br>
>> Ifat.<br>
>><br>
>><br>
>><br>
>> *From: *Muhammad Usman <<a href="mailto:usman@smartx.kr" target="_blank">usman@smartx.kr</a> <javascript:;>><br>
>> *Date: *Wednesday, 8 March 2017 at 13:36<br>
>> *To: *"Afek, Ifat (Nokia - IL)" <<a href="mailto:ifat.afek@nokia.com" target="_blank">ifat.afek@nokia.com</a> <javascript:;>><br>
>> *Cc: *JungSu Han <<a href="mailto:jshan@smartx.kr" target="_blank">jshan@smartx.kr</a> <javascript:;>><br>
>> *Subject: *Re: OpenStack Vitrage<br>
>><br>
>><br>
>><br>
>> Dear Ifat,<br>
>><br>
>> That's fine :).<br>
>><br>
>> Since, Vitrage project is already in mature phase and I don't have prior<br>
>> experience of working on the collaboration projects, so, that's why it's<br>
>> a<br>
>> little bit time taking to understand the stuff.<br>
>><br>
>> I attached the images for the topology (where square boxes are physical<br>
>> servers, oval shapes are virtual switches inside the box and on top we<br>
> have<br>
>> vm's) and errors I am encountering.<br>
>><br>
>><br>
>><br>
>> On Wed, Mar 8, 2017 at 6:20 PM, Afek, Ifat (Nokia - IL) <<br>
>> <a href="mailto:ifat.afek@nokia.com" target="_blank">ifat.afek@nokia.com</a> <javascript:;>> wrote:<br>
>><br>
>> Hi,<br>
>><br>
>><br>
>><br>
>> Sorry for not answering so far.<br>
>><br>
>><br>
>><br>
>> Can you please send the pictures as attachments? It is very hard to read<br>
>> them this way (both the topology diagram and the errors you had).<br>
>><br>
>> Regarding the Pike design sessions – I’m glad that you joined J we have<br>
>> discussed it in the last several IRC meetings, but only now I realize<br>
>> that<br>
>> maybe you were not aware of it. Sorry for that.<br>
>><br>
>><br>
>><br>
>> Best Regards,<br>
>><br>
>> Ifat.<br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> *From: *Muhammad Usman <<a href="mailto:usman@smartx.kr" target="_blank">usman@smartx.kr</a> <javascript:;>><br>
>> *Date: *Friday, 3 March 2017 at 04:31<br>
>> *To: *"Afek, Ifat (Nokia - IL)" <<a href="mailto:ifat.afek@nokia.com" target="_blank">ifat.afek@nokia.com</a> <javascript:;>><br>
>> *Cc: *JungSu Han <<a href="mailto:jshan@smartx.kr" target="_blank">jshan@smartx.kr</a> <javascript:;>><br>
>> *Subject: *Re: OpenStack Vitrage<br>
>><br>
>><br>
>><br>
>> Hi Ifat,<br>
>><br>
>> First of all, Regarding the virtual switches, I am not aware about any<br>
>> OpenStack project at the moment but we can add new Data Source by using<br>
> the<br>
>> ovs tools like (ovs-vsctl) and ovs logs. Below you can see some of our<br>
> work<br>
>> (using ovs-tools) where we show how (also states) virtual switches are<br>
>> connected to physical box and OpenStack Instances. For simplicity, we<br>
>> have<br>
>> fixed this topology.<br>
>><br>
>> [image: ne image 4]<br>
>><br>
>><br>
>><br>
>> *Vitrage Installation *<br>
>> I installed Vitrage using Devstack. However, I am experiencing some<br>
>> problems when querying the Vitrage either through cli or Horizon.<br>
>><br>
>> I am using OpenStack Newton Release (Stable branch) Single Machine Setup<br>
>> on Ubuntu 16.04 (Fresh Install).<br>
>><br>
>> This is the log from Vitrage-graph<br>
>> [image: ne image 2]<br>
>><br>
>><br>
>><br>
>> This is the log from the Horizon<br>
>><br>
>> [image: ne image 1]<br>
>><br>
>> View From Horizon<br>
>><br>
>> [image: ne image 3]<br>
>><br>
>> Here is the policy.json<br>
>> {<br>
>> "get topology": "",<br>
>> "get topology:all_tenants": "role:admin",<br>
>> "get resource": "",<br>
>> "list resources": "",<br>
>> "list alarms": "",<br>
>> "list alarms:all_tenants": "role:admin",<br>
>> "get rca": "",<br>
>> "get rca:all_tenants": "role:admin",<br>
>> "template validate": "",<br>
>> "template list": "",<br>
>> "template show": "",<br>
>> "event post": ""<br>
>> }<br>
>><br>
>> Here is the vitrage.conf<br>
>> [DEFAULT]<br>
>> debug = True<br>
>> transport_url = rabbit://stackrabbit:secret@x.<wbr>x.x.x:5672/<br>
>><br>
>> [oslo_policy]<br>
>> policy_file = /etc/vitrage/policy.json<br>
>><br>
>> [service_credentials]<br>
>> auth_url = <a href="http://x.x.x.x/identity" rel="noreferrer" target="_blank">http://x.x.x.x/identity</a><br>
>> region_name = RegionOne<br>
>> project_name = admin<br>
>> password = secret<br>
>> project_domain_id = default<br>
>> user_domain_id = default<br>
>> username = vitrage<br>
>> auth_type = password<br>
>><br>
>> [datasources]<br>
>> types = nova.host,nova.instance,nova.z<wbr>one,static_physical,cinder.<br>
>> volume,neutron.network,neutron<wbr>.port,heat.stack,doctor<br>
>><br>
>> [keystone_authtoken]<br>
>> memcached_servers = x.x.x.x:11211<br>
>> signing_dir = /var/cache/vitrage<br>
>> cafile = /opt/stack/data/ca-bundle.pem<br>
>> auth_uri = <a href="http://x.x.x.x/identity" rel="noreferrer" target="_blank">http://x.x.x.x/identity</a><br>
>> project_domain_name = Default<br>
>> project_name = admin<br>
>> user_domain_name = Default<br>
>> password = secret<br>
>> username = vitrage<br>
>> auth_url = <a href="http://x.x.x.x/identity_v2_admin" rel="noreferrer" target="_blank">http://x.x.x.x/identity_v2_adm<wbr>in</a><br>
>> auth_type = password<br>
>><br>
>> [api]<br>
>> pecan_debug = False<br>
>><br>
>> [entity_graph]<br>
>> datasources_values_dir = /etc/vitrage/datasources_value<wbr>s/<br>
>><br>
>> [static_physical]<br>
>> directory = /etc/vitrage/static_datasource<wbr>s/<br>
>> changes_interval = 30<br>
>> entities = switch<br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> On Wed, Mar 1, 2017 at 2:21 AM, Afek, Ifat (Nokia - IL) <<br>
>> <a href="mailto:ifat.afek@nokia.com" target="_blank">ifat.afek@nokia.com</a> <javascript:;>> wrote:<br>
>><br>
>> Hi,<br>
>><br>
>><br>
>><br>
>> Sorry for the late response, I was on vacation last week.<br>
>><br>
>><br>
>><br>
>> Vitrage visualization is implemented as an Horizon plugin, so it is<br>
>> written in “the Horizon way”. I think that our visualization issues are<br>
>> mainly around UX – when the entity graph becomes crowded, it is hard for<br>
>> the user to get meaningful information out of it. You can find some of<br>
>> our<br>
>> thoughts in the etherpad of the design session we had in the OpenStack<br>
>> Barcelona summit (look for the fishbowl session):<br>
>> <a href="https://etherpad.openstack.org/p/vitrage-barcelona-design-summit" rel="noreferrer" target="_blank">https://etherpad.openstack.org<wbr>/p/vitrage-barcelona-design-<wbr>summit</a><br>
>><br>
>><br>
>><br>
>> Did you already install Vitrage? If so, I think it would be best if you<br>
>> take a look at the UI by yourself and think what you would like to<br>
> improve.<br>
>><br>
>><br>
>><br>
>> Regarding the virtual switches – do you know of an OpenStack project (or<br>
>> another project) that provides this information?<br>
>><br>
>><br>
>><br>
>> Thanks,<br>
>><br>
>> Ifat.<br>
>><br>
>><br>
>><br>
>> *From: *Muhammad Usman <<a href="mailto:usman@smartx.kr" target="_blank">usman@smartx.kr</a> <javascript:;>><br>
>> *Date: *Sunday, 26 February 2017 at 15:32<br>
>><br>
>><br>
>> *To: *"Afek, Ifat (Nokia - IL)" <<a href="mailto:ifat.afek@nokia.com" target="_blank">ifat.afek@nokia.com</a> <javascript:;>><br>
>> *Cc: *JungSu Han <<a href="mailto:jshan@smartx.kr" target="_blank">jshan@smartx.kr</a> <javascript:;>><br>
>> *Subject: *Re: OpenStack Vitrage<br>
>><br>
>><br>
>><br>
>> Dear Ifat,<br>
>><br>
>> I am really sorry for delayed reply because I had to wind-up couple of<br>
>> urgent projects before getting involved in Vitrage project. However,<br>
>> meanwhile I tried to go through Vitrage documentations.<br>
>><br>
>> Sure, I would like to contribute in visualization part of Vitrage<br>
>> project.<br>
>> Can you let me know what are your current problems in visualization and<br>
>> what tools you are using. Since, I utilized JavaScript libraries for<br>
>> visualization of our Physical-Virtual resources topology visualization.<br>
>><br>
>> Furthermore, how about adding virtual switches (assisted by OpenvSwitch)<br>
>> between physical hosts and OpenStack instances because I don't see any<br>
>> option in the mentioned Use-cases?<br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> On Mon, Jan 16, 2017 at 9:32 PM, Afek, Ifat (Nokia - IL) <<br>
>> <a href="mailto:ifat.afek@nokia.com" target="_blank">ifat.afek@nokia.com</a> <javascript:;>> wrote:<br>
>><br>
>> Dear Muhammad,<br>
>><br>
>><br>
>><br>
>> Sounds great. If you are interested in the visualization area, we have a<br>
>> lot of challenges in Vitrage (displaying a very big topology graph in a<br>
> way<br>
>> that is usable is not trivial).<br>
>><br>
>> I will be happy to hear from you, and if you have any questions don’t<br>
>> hesitate to ask.<br>
>><br>
>><br>
>><br>
>> Best Regards,<br>
>><br>
>> Ifat.<br>
>><br>
>><br>
>><br>
>> *From: *Muhammad Usman <<a href="mailto:usman@smartx.kr" target="_blank">usman@smartx.kr</a> <javascript:;>><br>
>> *Date: *Monday, 16 January 2017 at 13:41<br>
>><br>
>><br>
>> *To: *"Afek, Ifat (Nokia - IL)" <<a href="mailto:ifat.afek@nokia.com" target="_blank">ifat.afek@nokia.com</a> <javascript:;>><br>
>> *Cc: *JungSu Han <<a href="mailto:jshan@smartx.kr" target="_blank">jshan@smartx.kr</a> <javascript:;>><br>
>> *Subject: *Re: OpenStack Vitrage<br>
>><br>
>><br>
>><br>
>> Dear Ifat,<br>
>><br>
>> We are covering some aspect of both visibility collection (monitoring<br>
>> data<br>
>> collection) using Open-source Monitoring Tools (e.g. Intel<br>
>> Snap-telemetry)<br>
>> and it's transformation to specific Visualizations (UI) according to our<br>
>> infrastructure requirements (e.g. topological view).<br>
>><br>
>> Regarding, the links you send to us, we already created the launchpad and<br>
>> gerrit accounts, also, subscribed to OpenStack-dev mailing list.<br>
>><br>
>> Currently, we are going through the Vitrage official documentation.<br>
>> Meanwhile, we will also try to install Vitrage in our testbed setup.<br>
>><br>
>> We will keep in touch with you to discuss further about our<br>
>> ideas/suggestions to Vitrage project.<br>
>><br>
>><br>
>><br>
>> On Fri, Jan 13, 2017 at 7:10 AM, Afek, Ifat (Nokia - IL) <<br>
>> <a href="mailto:ifat.afek@nokia.com" target="_blank">ifat.afek@nokia.com</a> <javascript:;>> wrote:<br>
>><br>
>> Dear Muhammad,<br>
>><br>
>><br>
>><br>
>> By visibility, do you mean UI? Or do you focus on monitoring?<br>
>><br>
>><br>
>><br>
>> Vitrage is a stable project that is now being used in production as part<br>
>> of Nokia products. However, while the base engine works well, there is a<br>
>> lot more to do in order to improve it: add more datasources (either for<br>
>> resources or new monitors), improve the templates language, identify new<br>
>> RCA use cases, and improve the UX. You can find here some ideas that we<br>
> put<br>
>> on our roadmap:<br>
>><br>
>> <a href="https://wiki.openstack.org/wiki/Vitrage/RoadMap" rel="noreferrer" target="_blank">https://wiki.openstack.org/wik<wbr>i/Vitrage/RoadMap</a><br>
>><br>
>><br>
>><br>
>> The list of tasks we are currently working on, as well as future ones can<br>
>> be found in launchpad:<br>
>><br>
>> <a href="https://blueprints.launchpad.net/vitrage" rel="noreferrer" target="_blank">https://blueprints.launchpad.n<wbr>et/vitrage</a><br>
>><br>
>><br>
>><br>
>> For the non-trivial blueprints we write an additional information in<br>
>> github. The following project holds the blueprints:<br>
>><br>
>> <a href="https://github.com/openstack/vitrage-specs" rel="noreferrer" target="_blank">https://github.com/openstack/v<wbr>itrage-specs</a><br>
>><br>
>><br>
>><br>
>> After being pushed to github, the blueprints are “compiled” and you can<br>
>> read the friendlier version in:<br>
>><br>
>> <a href="http://specs.openstack.org/openstack/vitrage-specs/" rel="noreferrer" target="_blank">http://specs.openstack.org/ope<wbr>nstack/vitrage-specs/</a><br>
>><br>
>><br>
>><br>
>> Vitrage code exists in three projects:<br>
>><br>
>> · <a href="https://github.com/openstack/vitrage" rel="noreferrer" target="_blank">https://github.com/openstack/<wbr>vitrage</a> - the main code<br>
>> (datasources, evaluator, notifiers)<br>
>><br>
>> · <a href="https://github.com/openstack/python-vitrageclient" rel="noreferrer" target="_blank">https://github.com/openstack/<wbr>python-vitrageclient</a> - api and cli<br>
>><br>
>> · <a href="https://github.com/openstack/vitrage-dashboard" rel="noreferrer" target="_blank">https://github.com/openstack/<wbr>vitrage-dashboard</a> - Horizon plugin<br>
>> for vitrage<br>
>><br>
>><br>
>><br>
>> Vitrage bugs are managed here:<br>
>><br>
>> <a href="https://bugs.launchpad.net/vitrage" rel="noreferrer" target="_blank">https://bugs.launchpad.net/vit<wbr>rage</a><br>
>><br>
>><br>
>><br>
>> So how do you start?<br>
>><br>
>> First, you should get familiar with OpenStack development process. Try to<br>
>> create a devstack, register to launchpad and gerrit, and also to<br>
>> OpenStack-dev mailing list.<br>
>><br>
>> Then, you can either suggest new blueprints (of features that you feel<br>
>> are<br>
>> missing or should be enhanced) or start by fixing bugs.<br>
>><br>
>><br>
>><br>
>> And of course, try to install and configure Vitrage. Understand how it<br>
>> works, and if you encounter a problem – suggest a solution and/or open a<br>
>> new bug. That’s a great way of starting.<br>
>><br>
>><br>
>><br>
>> Instructions on how to install Vitrage on top of devstack:<br>
>><br>
>> <a href="http://docs.openstack.org/developer/vitrage/installation-and-" rel="noreferrer" target="_blank">http://docs.openstack.org/deve<wbr>loper/vitrage/installation-<wbr>and-</a><br>
>> configuration.html<br>
>><br>
>><br>
>><br>
>> And in general, Vitrage official documentation is here:<br>
>> <a href="http://docs.openstack.org/developer/vitrage/" rel="noreferrer" target="_blank">http://docs.openstack.org/deve<wbr>loper/vitrage/</a><br>
>><br>
>><br>
>><br>
>> I hope I’m in the right direction. If not, or if you encounter any<br>
>> problem, don’t hesitate to ask me. You may also submit questions in<br>
>> openstack-dev mailing list with [vitrage] tag.<br>
>><br>
>><br>
>><br>
>> Best Regards,<br>
>><br>
>> Ifat.<br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> *From: *Muhammad Usman <<a href="mailto:usman@smartx.kr" target="_blank">usman@smartx.kr</a> <javascript:;>><br>
>> *Date: *Wednesday, 11 January 2017 at 11:57<br>
>> *To: *"Afek, Ifat (Nokia - IL)" <<a href="mailto:ifat.afek@nokia.com" target="_blank">ifat.afek@nokia.com</a> <javascript:;>><br>
>> *Cc: *JungSu Han <<a href="mailto:jshan@smartx.kr" target="_blank">jshan@smartx.kr</a> <javascript:;>><br>
>> *Subject: *Re: OpenStack Vitrage<br>
>><br>
>><br>
>><br>
>> Dear Ifat,<br>
>><br>
>> Thanks for your kind reply.<br>
>><br>
>> We are familiar with OpenStack project in general and also operating<br>
>> multiple versions of OpenStack cloud in our lab. However, we don't have<br>
> any<br>
>> development experience to OpenStack or other Open Source projects.<br>
>><br>
>> Overall, we both are working on visibility and monitoring Framework. It<br>
>> mainly involves integration and development of visibility and<br>
> visualization<br>
>> tools for SDN and Cloud-based environments.<br>
>><br>
>> When I said your assistance that means how we can start contributing to<br>
>> Vitrage project in design, development, or any other starter capacity?<br>
>> Especially, Visualization, RCA and extensions in Vitrage project<br>
>> regrading<br>
>> OVS or visibility sources.<br>
>><br>
>><br>
>><br>
>> On Tue, Jan 10, 2017 at 9:28 PM, Afek, Ifat (Nokia - IL) <<br>
>> <a href="mailto:ifat.afek@nokia.com" target="_blank">ifat.afek@nokia.com</a> <javascript:;>> wrote:<br>
>><br>
>> Dear Muhammad,<br>
>><br>
>><br>
>><br>
>> Thanks for your email, and for your interest in Vitrage. You are more<br>
>> than<br>
>> welcome to join our effort :-)<br>
>><br>
>><br>
>><br>
>> In order for me to better understand your needs, can you please tell me<br>
>> what your plans are regarding Vitrage? I’ll be happy to get a quick<br>
>> overview of what you are doing, where do you see Vitrage fit in, and what<br>
>> kind of contribution you would like to do.<br>
>><br>
>><br>
>><br>
>> When you talk about my assistance, what kind of assistance are you<br>
>> looking<br>
>> for? Are you familiar with OpenStack in general? If not, here are two<br>
> links<br>
>> that might help:<br>
>><br>
>> <a href="https://wiki.openstack.org/wiki/Getting_Started" rel="noreferrer" target="_blank">https://wiki.openstack.org/wik<wbr>i/Getting_Started</a><br>
>><br>
>> <a href="https://wiki.openstack.org/wiki/How_To_Contribute#How_can_I_help" rel="noreferrer" target="_blank">https://wiki.openstack.org/wik<wbr>i/How_To_Contribute#How_can_I_<wbr>help</a><br>
>><br>
>><br>
>><br>
>> And information about Vitrage:<br>
>><br>
>> <a href="https://wiki.openstack.org/wiki/Vitrage" rel="noreferrer" target="_blank">https://wiki.openstack.org/wik<wbr>i/Vitrage</a><br>
>><br>
>><br>
>><br>
>> If you have other questions, please don’t hesitate to ask.<br>
>><br>
>><br>
>><br>
>> Best Regards,<br>
>><br>
>> Ifat.<br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> *From: *Muhammad Usman <<a href="mailto:usman@smartx.kr" target="_blank">usman@smartx.kr</a> <javascript:;>><br>
>> *Date: *Tuesday, 10 January 2017 at 13:26<br>
>> *To: *"Afek, Ifat (Nokia - IL)" <<a href="mailto:ifat.afek@nokia.com" target="_blank">ifat.afek@nokia.com</a> <javascript:;>><br>
>> *Cc: *JungSu Han <<a href="mailto:jshan@smartx.kr" target="_blank">jshan@smartx.kr</a> <javascript:;>><br>
>> *Subject: *OpenStack Vitrage<br>
>><br>
>><br>
>><br>
>> Dear Ifat Afek,<br>
>><br>
>> We are two PhD students from NetCS lab (<a href="https://nm.gist.ac.kr/" rel="noreferrer" target="_blank">https://nm.gist.ac.kr/</a>). We are<br>
>> interested to contribute to OpenStack Vitrage project.<br>
>><br>
>> However, we don't have any prior experience in working on Open Source<br>
>> projects and their workflows.<br>
>><br>
>> So, in this regard, we require your assistance to how to start<br>
>> contributing to OpenStack Vitrage project.<br>
>><br>
>><br>
>><br>
>> --<br>
>><br>
>> Best Regards,<br>
>> Usman, Muhammad<br>
>> ******************************<wbr>**********************<br>
>> M.S./PhD Integrated candidate of Networked Computing Systems Lab.<br>
>> School of Information and Communications<br>
>> GIST (Gwangju Inst. of Sci. and Tech.)<br>
>> E-mail: <a href="mailto:usman@smartx.kr" target="_blank">usman@smartx.kr</a> <javascript:;><br>
>> Office: +82-62-715-2273<br>
>><br>
>><br>
>><br>
>><br>
>> --<br>
>><br>
>> Best Regards,<br>
>> Usman, Muhammad<br>
>> ******************************<wbr>**********************<br>
>> M.S./PhD Integrated candidate of Networked Computing Systems Lab.<br>
>> School of Information and Communications<br>
>> GIST (Gwangju Inst. of Sci. and Tech.)<br>
>> E-mail: <a href="mailto:usman@smartx.kr" target="_blank">usman@smartx.kr</a> <javascript:;><br>
>> Office: +82-62-715-2273<br>
>><br>
>><br>
>><br>
>><br>
>> --<br>
>><br>
>> Best Regards,<br>
>> Usman, Muhammad<br>
>> ******************************<wbr>**********************<br>
>> M.S./PhD Integrated candidate of Networked Computing Systems Lab.<br>
>> School of Information and Communications<br>
>> GIST (Gwangju Inst. of Sci. and Tech.)<br>
>> E-mail: <a href="mailto:usman@smartx.kr" target="_blank">usman@smartx.kr</a> <javascript:;><br>
>> Office: +82-62-715-2273<br>
>><br>
>><br>
>><br>
>><br>
>> --<br>
>><br>
>> Best Regards,<br>
>> Usman, Muhammad<br>
>> ******************************<wbr>**********************<br>
>> M.S./PhD Integrated candidate of Networked Computing Systems Lab.<br>
>> School of Information and Communications<br>
>> GIST (Gwangju Inst. of Sci. and Tech.)<br>
>> E-mail: <a href="mailto:usman@smartx.kr" target="_blank">usman@smartx.kr</a> <javascript:;><br>
>> Office: +82-62-715-2273<br>
>><br>
>><br>
>><br>
>><br>
>> --<br>
>><br>
>> Best Regards,<br>
>> Usman, Muhammad<br>
>> ******************************<wbr>**********************<br>
>> M.S./PhD Integrated candidate of Networked Computing Systems Lab.<br>
>> School of Information and Communications<br>
>> GIST (Gwangju Inst. of Sci. and Tech.)<br>
>> E-mail: <a href="mailto:usman@smartx.kr" target="_blank">usman@smartx.kr</a> <javascript:;><br>
>> Office: +82-62-715-2273<br>
>><br>
>><br>
>><br>
>><br>
>> --<br>
>><br>
>> Best Regards,<br>
>> Usman, Muhammad<br>
>> ******************************<wbr>**********************<br>
>> M.S./PhD Integrated candidate of Networked Computing Systems Lab.<br>
>> School of Information and Communications<br>
>> GIST (Gwangju Inst. of Sci. and Tech.)<br>
>> E-mail: <a href="mailto:usman@smartx.kr" target="_blank">usman@smartx.kr</a> <javascript:;><br>
>> Office: +82-62-715-2273<br>
>><br>
>><br>
>><br>
>><br>
>> --<br>
>><br>
>> Best Regards,<br>
>> Usman, Muhammad<br>
>> ******************************<wbr>**********************<br>
>> M.S./PhD Integrated candidate of Networked Computing Systems Lab.<br>
>> School of Information and Communications<br>
>> GIST (Gwangju Inst. of Sci. and Tech.)<br>
>> E-mail: <a href="mailto:usman@smartx.kr" target="_blank">usman@smartx.kr</a> <javascript:;><br>
>> Office: +82-62-715-2273<br>
>><br>
>><br>
>><br>
>><br>
>> --<br>
>><br>
>> Best Regards,<br>
>> Usman, Muhammad<br>
>> ******************************<wbr>**********************<br>
>> M.S./PhD Integrated candidate of Networked Computing Systems Lab.<br>
>> School of Information and Communications<br>
>> GIST (Gwangju Inst. of Sci. and Tech.)<br>
>> E-mail: <a href="mailto:usman@smartx.kr" target="_blank">usman@smartx.kr</a> <javascript:;><br>
>> Office: +82-62-715-2273<br>
>><br>
>><br>
>><br>
>><br>
>> --<br>
>><br>
>> Best Regards,<br>
>> Usman, Muhammad<br>
>> ******************************<wbr>**********************<br>
>> M.S./PhD Integrated candidate of Networked Computing Systems Lab.<br>
>> School of Information and Communications<br>
>> GIST (Gwangju Inst. of Sci. and Tech.)<br>
>> E-mail: <a href="mailto:usman@smartx.kr" target="_blank">usman@smartx.kr</a> <javascript:;><br>
>> Office: +82-62-715-2273<br>
>><br>
><br>
><br>
><br>
> --<br>
> Best Regards,<br>
> Usman, Muhammad<br>
> ******************************<wbr>**********************<br>
> M.S./PhD Integrated candidate of Networked Computing Systems Lab.<br>
> School of Information and Communications<br>
> GIST (Gwangju Inst. of Sci. and Tech.)<br>
> E-mail: <a href="mailto:usman@smartx.kr" target="_blank">usman@smartx.kr</a> <javascript:;><br>
> Office: +82-62-715-2273<br>
><br>
><br>
><br>
> --<br>
> Best Regards,<br>
> Usman, Muhammad<br>
> ******************************<wbr>**********************<br>
> M.S./PhD Integrated candidate of Networked Computing Systems Lab.<br>
> School of Information and Communications<br>
> GIST (Gwangju Inst. of Sci. and Tech.)<br>
> E-mail: <a href="mailto:usman@smartx.kr" target="_blank">usman@smartx.kr</a><br>
> Office: +82-62-715-2273<br>
><br>
<br>
<br>
--<br>
--<br>
*<br>
Regards*<br>
*<br>
Muhammad Usman*<br>
Application Engineer<br>
LMK Resources (pvt) Limited<br>
<a href="http://www.lmkr.com" rel="noreferrer" target="_blank">www.lmkr.com</a><br>
+92 (323) 5599 068*<br>
*<br>
<br>
</div></div> ______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
<br>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
</blockquote></div><br></div>