fosshelp: May 2015

Thursday, May 28, 2015

OpenStack neutron CLI create security group rule

Wednesday, May 27, 2015

sudo apt-get update E: Some index files failed to download. They have been ignored, or old ones used instead.

===========#sudo apt-get update, Error==========

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/saucy/main/source/Sources 404 Not Found [IP: 91.189.91.24 80]

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/saucy/restricted/source/Sources 404 Not Found [IP: 91.189.91.24 80]

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/saucy/universe/source/Sources 404 Not Found [IP: 91.189.91.24 80]

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/saucy/multiverse/source/Sources 404 Not Found [IP: 91.189.91.24 80]

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/saucy/main/binary-amd64/Packages 404 Not Found [IP: 91.189.91.24 80]

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/saucy/restricted/binary-amd64/Packages 404 Not Found [IP: 91.189.91.24 80]

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/saucy/universe/binary-amd64/Packages 404 Not Found [IP: 91.189.91.24 80]

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/saucy/multiverse/binary-amd64/Packages 404 Not Found [IP: 91.189.91.24 80]

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/saucy/main/binary-i386/Packages 404 Not Found [IP: 91.189.91.24 80]

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/saucy/restricted/binary-i386/Packages 404 Not Found [IP: 91.189.91.24 80]

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/saucy/universe/binary-i386/Packages 404 Not Found [IP: 91.189.91.24 80]

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/saucy/multiverse/binary-i386/Packages 404 Not Found [IP: 91.189.91.24 80]

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/saucy-updates/main/source/Sources 404 Not Found [IP: 91.189.91.24 80]

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/saucy-updates/restricted/source/Sources 404 Not Found [IP: 91.189.91.24 80]

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/saucy-updates/universe/source/Sources 404 Not Found [IP: 91.189.91.24 80]

E: Some index files failed to download. They have been ignored, or old ones used instead.

======Fix======

Replace http://archive.ubuntu.com/ with http://old-releases.ubuntu.com in /etc/apt/sources.list

#sudo sed -i -e 's/archive.ubuntu.com\|security.ubuntu.com/old-releases.ubuntu.com/g' /etc/apt/sources.list

#sudo apt-get update

Tuesday, May 26, 2015

How To GitHub delete a commit

1)
Clone the repo to your machine.
#git clone https://github.com/sajuptpm/tools.git

2)
Find ID of the commit which comes just before the commit which you want to delete.
You can use the command "#git log -n 10" for that.

3)
Then use this command:
#git rebase -i commit_id

Your text editor will open with a file that lists all the commits which come after your selected commit_id, and in front of each commit there is the word "pick".

In that list remove the commit which you want to delete and save it.

4)
Force-push to remote repo.

#git push -f origin master

5)
Check github. It should be updated

How To GitHub change commit message

1)
Clone the repo to your machine.
#git clone https://github.com/sajuptpm/tools.git

2)
Find ID of the commit which comes just before the commit for which you want to change the message.
You can use the command "#git log -n 10" for that.

3)
Then use this command:
#git rebase -i commit_id

Your text editor will open with a file that lists all the commits which come after your selected commit_id, and in front of each commit there is the word "pick".

The commit for which you want to change the commit message, change "pick" to "reword" and save it.

Then a new file should pop up in your editor.There you can change the commit message and save it

4)
Force-push to remote repo.

#git push -f origin master

5)
Check github. It should be updated.

How to Rebase a Pull Request

https://github.com/edx/edx-platform/wiki/How-to-Rebase-a-Pull-Request

http://eli.thegreenplace.net/2014/02/19/squashing-github-pull-requests-into-a-single-commit

1)
#cd puppet-rjil

#git branch
* contrail_quota
master

2)
#git remote -v
origin    https://github.com/sajuptpm/puppet-rjil.git (fetch)
origin    https://github.com/sajuptpm/puppet-rjil.git (push)

3)
Add official remote

a)
#git remote add official_remote https://github.com/JioCloud/puppet-rjil.git

b)
#git remote -v
official_remote    https://github.com/JioCloud/puppet-rjil.git (fetch)
official_remote    https://github.com/JioCloud/puppet-rjil.git (push)
origin    https://github.com/sajuptpm/puppet-rjil.git (fetch)
origin    https://github.com/sajuptpm/puppet-rjil.git (push)

4)
Fetch the latest version of master

a)
#git fetch official_remote

remote: Counting objects: 4, done.
remote: Compressing objects: 100% (4/4), done.
remote: Total 4 (delta 0), reused 0 (delta 0), pack-reused 0
Unpacking objects: 100% (4/4), done.
From https://github.com/JioCloud/puppet-rjil
* [new branch]      master     -> official_remote/master
* [new branch]      qaenv      -> official_remote/qaenv
* [new branch]      revert-587-add-keys-yatin -> official_remote/revert-587-add-keys-yatin
* [new branch]      testenv    -> official_remote/testenv

b)
#git branch
* contrail_quota
master

5)
Squash your changes.

This step is not always necessary, but is required when your commit history
is full of small, unimportant commits (such as "Fix pep8", "Add tests").
It involves taking all the commits you've made on your branch, and squashing
them all into one, larger commit. Doing this makes it easier for you to resolve
conflicts while performing the rebase, and easier for us to review your pull request.

a)
First, find the commit (commit id) that is base of your branch using the command "git merge-base".
That command will return a commit hash (id).
Or
you can find the commit id using "#git log -n 10" command.

#git merge-base master
#git merge-base contrail_quota master
cf390dff46cd1492e4fe5cfc932975c026133444

b)
If your merge base commit hash (id) is abc123, you would run "$ git rebase --interactive abc123".
Your text editor will open with a file that lists all the commits in your branch,
and in front of each commit is the word "pick". It looks something like this:

#git rebase --interactive cf390dff46cd1492e4fe5cfc932975c026133444

----

pick 0754175 set default quota in contrail
pick a354793 temp change for testing
pick d13540f updated quota values for testing
pick 3213161 added saju's ssh pub key
pick f4e5c53 updated quota value for testing

c)
Then arrange it based on your requirement.
You want to replace the word "pick" with the word "squash" or "s".
I want to make it as two commits.

commit1 = 0754175 + d13540f + f4e5c53
commit2 = 3213161 + a354793

So I arranged it like this:

----

pick 0754175 set default quota in contrail
squash d13540f updated quota values for testing
squash f4e5c53 updated quota value for testing

pick 3213161 added saju's ssh pub key
squash a354793 temp change for testing

-------

Save and close the file, and a moment later a new file should pop up in your editor,
combining all the commit messages of all the commits. Reword (change) this commit
message as you want, and then save and close that file as well.
This commit message will be the commit message for the one, big commit that you
are squashing all of your larger commits into. Once you've saved and closed that
file, your commits have been squashed together, and you're done with this step.

6)
How to reword/change commit message if you want
To reword/change commit message, use the command "reword".
For example you might perform an interactive rebase and replace this:

a)
#git rebase --interactive cf390dff46cd1492e4fe5cfc932975c026133444

It looks something like this:

pick 3581104 set default quota in contrail
pick cc43285 added saju's ssh pub key

b)
You want to replace the word "pick" of commit you want to change message with the word "reword".
It looks something like this:

reword 3581104 set default quota in contrail
pick cc43285 added saju's ssh pub key

-----

Save and close the file, and a moment later a new file should pop up in your editor,
showing you the current wording of the commit message.
Reword this commit message as you want, and then save and close that file as well.
This commit message will be the new commit message for your commit,

7)
Perform the rebase

a)
Note the id of commit which comes just before your first commit in this branch.
#git log -n 4

b)
#git branch
* contrail_quota
master

b)
#git rebase official_remote/master
First, rewinding head to replay your work on top of it...
Applying: set default quota in contrail
Applying: added saju's ssh pub key

c)
Again, Note the id of commit which comes just before your first commit in this branch.
There should be some differents if there was some new commits in the master of official repo.
#git log -n 4

----
Git will start replaying your commits onto the latest version of master.
You may get conflicts while doing so: if you do, git will pause and ask you to
resolve the conflicts before continuing. This is exactly like resolving conflicts
with a merge: you can use git status to see which files are in conflict, edit
the files to resolve the conflicts, and then use git add to indicate that the
conflicts have been resolved. However, instead of running git commit,
you instead want to run git rebase --continue to indicate to git that it should
continue replaying your commits. If you've squashed your commits before doing
this step, you'll only have to pause to resolve conflicts once -- if you didn't
squash, you may have to resolve your conflicts multiple times.

8)
Force-push to update your pull request

As explained above, when you do a rebase, you are changing the history on your
branch. As a result, if you try to do a normal git push after a rebase, git will
reject it because there isn't a direct path from the commit on the server to the
commit on your branch. Instead, you'll need to use the -f or --force flag to tell
git that yes, you really know what you're doing. When doing force pushes,
it is highly recommended that you set your push.default config setting to simple,
which is the default in Git 2.0. To make sure that your config is correct, run:

#git config --global push.default simple

Once it's correct, you can just run:

#git push -f origin contrail_quota

And check your pull request. It should be updated!

Saturday, May 23, 2015

How to install Desktop Screen Recorder Kazam in ubuntu

sudo apt-get install kazam

Thursday, May 21, 2015

puppet ruby rspec: gsub example

1)
#vim exampl2.erb

##9 spaces i given. gsub removes first 8 spaces from lines which start with space.

print " HelloSaju".gsub(/^ {8}/, '')

print "\n"

2)
#vim example1.erb

print <<-api b="">.gsub(/^ {8}/, '')
        [DEFAULTS]
        ifmap_server_ip=10.1.1.1
        ifmap_server_port=8443
        ifmap_username=api-server
        ifmap_password=api-server

        [SECURITY]
        use_certs=false
        keyfile=/etc/contrail/ssl/private_keys/apiserver_key.pem
        certfile=/etc/contrail/ssl/certs/apiserver.pem
        ca_certs=/etc/contrail/ssl/certs/ca.pem

        [KEYSTONE]
        auth_host=10.1.1.2
        auth_protocol=http
        auth_port=35357
        admin_user=admin
        admin_password=admin_password
        admin_token=admin_token
        admin_tenant_name=openstack
      API

print "\n"

set default quota values in /etc/contrail/contrail-api.conf

#sudo vim /etc/contrail/contrail-api.conf

[QUOTA]
virtual_network=6
subnet=25
floating_ip=10
logical_router=20
security_group=60
security_group_rule=60
virtual_machine_interface=30

Wednesday, May 20, 2015

How to post html code in your blog

1)
Goto following site and paste your html code and copy the encoded html
http://www.dan.co.jp/cases/javascript/encode_entities.html

2)
Paste encoded html in your blog inside the <pre> </pre> tag

OpenContrail XMPP Message

1)
* 5269 : XMPP Server Port (Control Node)

2)
iq - messages
================

a)
Similar to http GET and POST

Example of request "iq" message:
---------------------------------

<iq
    to='book.lit'
    type='get'
    id='disco:l'>    

    <query xmlns='disco#info'/>

</iq>

* type='get' is equal to http GET
* type='set' is equal to http POST

* Every "iq" message has "id" and that should be unique.
* Request "iq" message and response "iq" message will contain same "id", so it can track correct response message.
* Here "<query xmlns='disco#info'/>" is the child tag, which tell which extension protocol is using.
* Here "query" tag contains, what is requesting.
* Here the namespace "xmlns='disco#info'" means that it uses service discovery extension protocol.

Example of response "iq" message:
----------------------------------

<iq
    to='romeo@book.lit/home'
    from='book.lit'
    type='result'
    id='disco:l'
    <query xmlns='disco#info'>
        <identity category='server'
        type='im'
        name='ejabberd'/>
        <feature var='vard-temp'/>
    </query>
</iq>

* "type='result'" indicate that it is a response.
* Here "id='disco:l'" match with "id" in the request "iq" message
* Here "query" tag contains the result or response of the request.
* "<identity .... />" is the service discovery result or response message.

3)
Long polling
-------------
* Bidirectional Streams Over Synchronous Http (BOSH) - Long polling

* Difference Long polling and Normal polling

- Normal polling:
* client send request to Server and Server reply immediatly (with result or without result). Client repeat this after a specific interval.

- Long polling:
* client send request to Server and that request wait (long time/specific time) in server side until something new comes in the server and server reply when something new comes. So here request is waiting in server for log time for the response. Here client should wait long time for the response and send new request after a specific time, if there is no response, that time server will discard the previous request.

4)
set/post "iq" request to "config" to subscribe on node "virtual-machine:3654ee7d-02d6-4a16-b526-304d559488a7"
---------------------------------------------------

<?xml version="1.0"?>


<iq type="set"
     from="ubuntu"
     to="network-control@contrailsystems.com/config">


    <pubsub xmlns="http://jabber.org/protocol/pubsub">


        <subscribe node="virtual-machine:3654ee7d-02d6-4a16-b526-304d559488a7"/>


    </pubsub>


</iq>

5)
set/post "iq" request to "bgp-peer" to subscribe on node "default-domain:demo:mynw1:mynw1"
--------------------------------------------------------------------

<?xml version="1.0"?>


<iq type="set"
     from="ubuntu"
     to="network-control@contrailsystems.com/bgp-peer"
     id="subscribe4">
    
    
    <pubsub xmlns="http://jabber.org/protocol/pubsub">
        
        
        <subscribe node="default-domain:demo:mynw1:mynw1">
            
            
            <options>
                
                
                <instance-id>
                    3
                </instance-id>
                
                
            </options>
            
            
        </subscribe>
        
        
    </pubsub>
    
    
</iq>

6)
set/post "iq" request to "config" for update
---------------------------------------------
* It update 'routing-instance' 'default-domain:demo:mynw1:mynw1'
* It update the link between 'instance-ip 1524eea3-e387-4f3f-aa8a-1dea528edf2f' and 'virtual-network default-domain:demo:mynw1'
* etc ---


<?xml version="1.0"?>


<iq type="set"
     from="network-control@contrailsystems.com"
     to="default-global-system-config:ubuntu/config">
    
        
    <config>
        
                
        <update>
            
                        
            <node type="routing-instance">
                
                                
                <name>
                    default-domain:demo:mynw1:mynw1
                </name>
                
                            
            </node>
            
                        
            <link>
                
                                
                <node type="virtual-machine-interface-routing-instance">
                    
                                        
                    <name>
                        attr(default-domain:demo:dbc7b522-dd36-44c3-ae91-c9f4a455ddff,default-domain:demo:mynw1:mynw1)
                    </name>
                    
                                    
                </node>
                
                                
                <node type="routing-instance">
                    
                                        
                    <name>
                        default-domain:demo:mynw1:mynw1
                    </name>
                    
                                    
                </node>
                
                                
                <metadata type="virtual-machine-interface-routing-instance"/>
                
                            
            </link>
            
                        
            <link>
                
                                
                <node type="instance-ip">
                    
                                        
                    <name>
                        1524eea3-e387-4f3f-aa8a-1dea528edf2f
                    </name>
                    
                                    
                </node>
                
                                
                <node type="virtual-network">
                    
                                        
                    <name>
                        default-domain:demo:mynw1
                    </name>
                    
                                    
                </node>
                
                                
                <metadata type="instance-ip-virtual-network"/>
                
                            
            </link>
            
                        
            <node type="virtual-network-network-ipam">
                
                                
                <name>
                    attr(default-domain:default-project:default-network-ipam,default-domain:demo:mynw1)
                </name>
                
                                
                <value>
                    
                                        
                    <ipam-subnets>
                        
                                                
                        <subnet>
                            
                                                        
                            <ip-prefix>
                                10.1.1.0
                            </ip-prefix>
                            
                                                        
                            <ip-prefix-len>
                                24
                            </ip-prefix-len>
                            
                                                    
                        </subnet>
                        
                                                
                        <default-gateway>
                            10.1.1.1
                        </default-gateway>
                        
                                                
                        <dns-server-address>
                        </dns-server-address>
                        
                                                
                        <subnet-uuid>
                            b77692a2-aea4-41fc-92de-28a9fa703f12
                        </subnet-uuid>
                        
                                                
                        <enable-dhcp>
                            true
                        </enable-dhcp>
                        
                                                
                        <addr_from_start>
                            true
                        </addr_from_start>
                        
                                                
                        <dhcp-option-list/>
                        
                                                
                        <host-routes/>
                        
                                                
                        <subnet-name>
                            subnet1
                        </subnet-name>
                        
                                            
                    </ipam-subnets>
                    
                                        
                    <host-routes/>
                    
                                    
                </value>
                
                            
            </node>
            
                        
            <link>
                
                                
                <node type="virtual-network">
                    
                                        
                    <name>
                        default-domain:demo:mynw1
                    </name>
                    
                                    
                </node>
                
                                
                <node type="virtual-network-network-ipam">
                    
                                        
                    <name>
                        attr(default-domain:default-project:default-network-ipam,default-domain:demo:mynw1)
                    </name>
                    
                                    
                </node>
                
                                
                <metadata type="virtual-network-network-ipam"/>
                
                            
            </link>
            
                        
            <link>
                
                                
                <node type="virtual-network">
                    
                                        
                    <name>
                        default-domain:demo:mynw1
                    </name>
                    
                                    
                </node>
                
                                
                <node type="routing-instance">
                    
                                        
                    <name>
                        default-domain:demo:mynw1:mynw1
                    </name>
                    
                                    
                </node>
                
                                
                <metadata type="virtual-network-routing-instance"/>
                
                            
            </link>
            
                        
            <node type="network-ipam">
                
                                
                <name>
                    default-domain:default-project:default-network-ipam
                </name>
                
                                
                <id-perms>
                    
                                        
                    <permissions>
                        
                                                
                        <owner>
                            cloud-admin
                        </owner>
                        
                                                
                        <owner-access>
                            7
                        </owner-access>
                        
                                                
                        <group>
                            cloud-admin-group
                        </group>
                        
                                                
                        <group-access>
                            7
                        </group-access>
                        
                                                
                        <other-access>
                            7
                        </other-access>
                        
                                            
                    </permissions>
                    
                                        
                    <uuid>
                        
                                                
                        <uuid-mslong>
                            2800209106097422692
                        </uuid-mslong>
                        
                                                
                        <uuid-lslong>
                            11079038519831513023
                        </uuid-lslong>
                        
                                            
                    </uuid>
                    
                                        
                    <enable>
                        true
                    </enable>
                    
                                        
                    <created>
                        2015-02-12T11:50:12
                    </created>
                    
                                        
                    <last-modified>
                        2015-02-12T11:50:12
                    </last-modified>
                    
                                        
                    <description>
                    </description>
                    
                                        
                    <user-visible>
                        true
                    </user-visible>
                    
                                    
                </id-perms>
                
                            
            </node>
            
                        
            <link>
                
                                
                <node type="virtual-network-network-ipam">
                    
                                        
                    <name>
                        attr(default-domain:default-project:default-network-ipam,default-domain:demo:mynw1)
                    </name>
                    
                                    
                </node>
                
                                
                <node type="network-ipam">
                    
                                        
                    <name>
                        default-domain:default-project:default-network-ipam
                    </name>
                    
                                    
                </node>
                
                                
                <metadata type="virtual-network-network-ipam"/>
                
                            
            </link>
            
                    
        </update>
        
            
    </config>
    
    
</iq>

7)
set/post "iq" request to "config" for delete
---------------------------------------------
* It delete the link between 'instance-ip 1524eea3-e387-4f3f-aa8a-1dea528edf2f' and 'virtual-network default-domain:demo:mynw1'


<?xml version="1.0"?>


<iq type="set"
     from="network-control@contrailsystems.com"
     to="default-global-system-config:ubuntu/config">
    
        
    <config>
        
                
        <delete>
            
                        
            <link>
                
                                
                <node type="instance-ip">
                    
                                        
                    <name>
                        1524eea3-e387-4f3f-aa8a-1dea528edf2f
                    </name>
                    
                                    
                </node>
                
                                
                <node type="virtual-network">
                    
                                        
                    <name>
                        default-domain:demo:mynw1
                    </name>
                    
                                    
                </node>
                
                                
                <metadata type="instance-ip-virtual-network"/>
                
                            
            </link>
            
                    
        </delete>
        
            
    </config>
    
    
</iq>

Tuesday, May 19, 2015

fatal error: pcap.h: No such file or directory

Fix:
=====

#sudo apt-get install libpcap0.8-dev

OR

#wget http://mirror.esc7.net/pub/Ubuntu/pool/main/libp/libpcap/libpcap0.8-dev_1.4.0-2_amd64.deb

#sudo gdebi libpcap0.8-dev_1.4.0-2_amd64.deb

Contrail Analytics APIs and User Visible Entities (UVEs)

http://192.168.56.102:8081/analytics/uves

[{'href': 'http://192.168.56.102:8081/analytics/uves/service-chains',
'name': 'service-chains'},
{'href': 'http://192.168.56.102:8081/analytics/uves/config-nodes',
'name': 'config-nodes'},
{'href': 'http://192.168.56.102:8081/analytics/uves/storage-pools',
'name': 'storage-pools'},
{'href': 'http://192.168.56.102:8081/analytics/uves/xmpp-peers',
'name': 'xmpp-peers'},
{'href': 'http://192.168.56.102:8081/analytics/uves/vrouters',
'name': 'vrouters'},
{'href': 'http://192.168.56.102:8081/analytics/uves/generators',
'name': 'generators'},
{'href': 'http://192.168.56.102:8081/analytics/uves/service-instances',
'name': 'service-instances'},
{'href': 'http://192.168.56.102:8081/analytics/uves/bgp-peers',
'name': 'bgp-peers'},
{'href': 'http://192.168.56.102:8081/analytics/uves/analytics-nodes',
'name': 'analytics-nodes'},
{'href': 'http://192.168.56.102:8081/analytics/uves/virtual-networks',
'name': 'virtual-networks'},
{'href': 'http://192.168.56.102:8081/analytics/uves/control-nodes',
'name': 'control-nodes'},
{'href': 'http://192.168.56.102:8081/analytics/uves/databases',
'name': 'databases'},
{'href': 'http://192.168.56.102:8081/analytics/uves/virtual-machines',
'name': 'virtual-machines'},
{'href': 'http://192.168.56.102:8081/analytics/uves/storage-osds',
'name': 'storage-osds'},
{'href': 'http://192.168.56.102:8081/analytics/uves/servers',
'name': 'servers'},
{'href': 'http://192.168.56.102:8081/analytics/uves/dns-nodes',
'name': 'dns-nodes'},
{'href': 'http://192.168.56.102:8081/analytics/uves/storage-disks',
'name': 'storage-disks'}]

1)
OpenContrail find NodeStatus,ConfigCpuState and ModuleCpuState of Config Node

http://192.168.56.102:8081/analytics/uves/config-nodes
http://192.168.56.102:8081/analytics/uves/config-node/ubuntu
http://192.168.56.102:8081/analytics/uves/config-node/ubuntu?cfilt=NodeStatus
http://192.168.56.102:8081/analytics/uves/config-node/ubuntu?cfilt=ConfigCpuState
http://192.168.56.102:8081/analytics/uves/config-node/ubuntu?cfilt=ModuleCpuState

2)
http://192.168.56.102:8081/analytics/uves/xmpp-peers
http://192.168.56.102:8081/analytics/uves/xmpp-peer/ubuntu:192.168.56.102
http://192.168.56.102:8081/analytics/uves/xmpp-peer/ubuntu:192.168.56.102?cfilt=XmppPeerInfoData

3)
http://192.168.56.102:8081/analytics/uves/vrouters
http://192.168.56.102:8081/analytics/uves/vrouter/ubuntu
http://192.168.56.102:8081/analytics/uves/vrouter/ubuntu?cfilt=VrouterStatsAgent
http://192.168.56.102:8081/analytics/uves/vrouter/ubuntu?cfilt=NodeStatus
http://192.168.56.102:8081/analytics/uves/vrouter/ubuntu?cfilt=VrouterAgent
http://192.168.56.102:8081/analytics/uves/vrouter/ubuntu?cfilt=ComputeCpuState

4)
http://192.168.56.102:8081/analytics/uves/analytics-nodes
http://192.168.56.102:8081/analytics/uves/analytics-node/ubuntu?cfilt=NodeStatus
http://192.168.56.102:8081/analytics/uves/analytics-node/ubuntu?cfilt=AnalyticsCpuState
http://192.168.56.102:8081/analytics/uves/analytics-node/ubuntu?cfilt=ModuleCpuState
http://192.168.56.102:8081/analytics/uves/analytics-node/ubuntu?cfilt=QueryPerfInfo
http://192.168.56.102:8081/analytics/uves/analytics-node/ubuntu?cfilt=CollectorState

5)
http://192.168.56.102:8081/analytics/uves/virtual-networks
http://192.168.56.102:8081/analytics/uves/virtual-network/default-domain:default-project:default-virtual-network

6)
http://192.168.56.102:8081/analytics/uves/control-nodes
http://192.168.56.102:8081/analytics/uves/control-node/ubuntu
http://192.168.56.102:8081/analytics/uves/control-node/ubuntu?cfilt=NodeStatus
http://192.168.56.102:8081/analytics/uves/control-node/ubuntu?cfilt=BgpRouterState
http://192.168.56.102:8081/analytics/uves/control-node/ubuntu?cfilt=ControlCpuState

7)
http://192.168.56.102:8081/analytics/uves/databases
http://192.168.56.102:8081/analytics/uves/database/ubuntu

8)
http://192.168.56.102:8081/analytics/uves/virtual-machines
http://192.168.56.102:8081/analytics/uves/virtual-machine/6767c744-3f47-458a-b61f-0bde1b5f10d9
http://192.168.56.102:8081/analytics/uves/virtual-machine/6767c744-3f47-458a-b61f-0bde1b5f10d9?cfilt=VirtualMachineStats
http://192.168.56.102:8081/analytics/uves/virtual-machine/6767c744-3f47-458a-b61f-0bde1b5f10d9?cfilt=UveVirtualMachineAgent

9)
http://192.168.56.102:8081/analytics/uves/dns-nodes
http://192.168.56.102:8081/analytics/uves/dns-node/ubuntu

10)
http://192.168.56.102:8081/analytics/uves/storage-disks

11)
http://192.168.56.102:8081/analytics/uves/servers

12)
http://192.168.56.102:8081/analytics/uves/storage-osds

13)
http://192.168.56.102:8081/analytics/uves/service-chains

14)
http://192.168.56.102:8081/analytics/uves/storage-pools

15)
http://192.168.56.102:8081/analytics/uves/generators

16)
http://192.168.56.102:8081/analytics/uves/service-instances

17)
http://192.168.56.102:8081/analytics/uves/bgp-peers

fosshelp