Marco,

Apart from changes done by Josef we faced few more issue. Some were related to 
HeatBridge and some related to the image we used for vFw and vLb.


1.       Rackspace needs tenant id( or may be name and id is same hence doesn’t 
make a difference in Rackspace) for authentication whereas Openstack Mitaka is 
using the tenant name for authentication.

Because of which at the Heat Bridge step we were getting authentication error. 
We changed few python files to overcome this error.



a.       robot\library\heatbridge\HeatBridge.py (adding extra parameter 
tenantName )



Before :

    def init_bridge(self, openstack_identity_url, username, password, tenant, 
region, owner):

        self.om = OpenstackManager(openstack_identity_url, 
OpenstackContext(username, password, tenant, region, owner));

        self.am = AAIManager(OpenstackContext(username, password, tenant, 
region, owner));


                        after :
                        def init_bridge(self, openstack_identity_url, username, 
password, tenant, region, owner, tenantName):
                           self.om = OpenstackManager(openstack_identity_url, 
OpenstackContext(username, password, tenantName, region, owner,tenantName));
                            self.am = AAIManager(OpenstackContext(username, 
password, tenant, region, owner,tenantName));


b.      robot\library\heatbridge\OpenstackContext.py (adding extra parameter 
tenantName )



class OpenstackContext:

    """OpenstackContext is a simple class that holds the provided information 
that heatbridge uses."""



    #this holds the info of the openstack clients

    username = None;

    password = None;

    tenant = None;

    region = None;

    owner = None;

    tenantName= None;



    def __init__(self, username, password, tenant, region, owner,tenantName):

        self.username = username;

        self.password = password;

        self.tenant = tenant;

        self.region = region;

        self.owner = owner;

        self.tenantName = tenantName;



c.       \robot\resources\heatbridge.robot



Init Bridge    ${openstack_identity_url}    ${user}    ${pass}    ${tenant_id}  
  ${region}   ${GLOBAL_AAI_CLOUD_OWNER}   
${GLOBAL_VM_PROPERTIES['openstack_tenant']}


d.      /share/config/vm_properties.py



"openstack_tenant" : "<your tenant Name>",




2.       \robot\library\heatbridge\OpenstackManager.py (adding api version)

self.__neutron_client.action_prefix = "/v2.0";


3.       Image we used for fw,pg and snk is a simple Ubuntu image. Changes we 
have done might not be required for all .

a.       SSH login was not getting successful during the validation stage so we 
had to add below lines to the files.



  cat /root/.ssh/authorized_keys | awk {'print $14" "$15" "$16'} > 
/tmp/authorized_keys

            cp /tmp/authorized_keys /root/.ssh/authorized_keys



b.      Adding default gateway and interface  to the iptable



    route del -net 0.0.0.0/0

            route add -net 0.0.0.0/0 gw <public gateway ip>

            echo "auto eth2" >> /etc/network/interfaces

            echo "iface eth2 inet dhcp" >> /etc/network/interfaces

            echo "auto eth3" >> /etc/network/interfaces

            echo "iface eth3 inet dhcp" >> /etc/network/interfaces

            ifup eth2

            ifup eth3

c.       Maven dependency failure with error “Peer not authenticated.” Added 
below statement to all mvn commands.

mvn org.apache.maven.plugins:maven-dependency-plugin:2.10:get 
-DremoteRepositories=$REPO_URL_ARTIFACTS 
-Dartifact=org.openecomp.demo.vnf:sample-distribution:$DEMO_ARTIFACTS_VERSION:tar.gz:hc
 -Dtransitive=false -Ddest=. -Dmaven.wagon.http.ssl.insecure=true 
-Dmaven.wagon.http.ssl.allowall=true



d.      Flush all the iptable rules which was filtering the packets from 
flowing.

     iptables -F

            iptables -P INPUT ACCEPT

            iptables -P FORWARD ACCEPT

            iptables -P OUTPUT ACCEPT



Let me know if you think this can be useful for others.

Regards,
Tapan M


From: PLATANIA, MARCO (MARCO) [mailto:[email protected]]
Sent: Thursday, July 06, 2017 6:45 PM
To: Josef Reisinger <[email protected]>; Tapan Majhi 
<[email protected]>
Cc: [email protected]
Subject: Re: [onap-discuss] [DOC] Documentation for running demo on Openstack 
Mitaka

Josef, Tapan,

Documenting your progress is a good idea! The heat templates for vLB and vFW 
that are currently in Gerrit work with OpenStack Liberty.

Tapan,

What changes did you make for Mitaka?

Thanks,
Marco

From: 
<[email protected]<mailto:[email protected]>>
 on behalf of Josef Reisinger 
<[email protected]<mailto:[email protected]>>
Date: Thursday, July 6, 2017 at 9:11 AM
To: "MAJHI, TAPAN" <[email protected]<mailto:[email protected]>>
Cc: "[email protected]<mailto:[email protected]>" 
<[email protected]<mailto:[email protected]>>
Subject: Re: [onap-discuss] [DOC] Documentation for running demo on Openstack 
Mitaka

Hi Tapan,

I started a similar activity with pages under 
https://wiki.onap.org/display/DW/Tutorial%3A+Creating+a+Service+Instance+from+a+Design+Model<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Tutorial-253A-2BCreating-2Ba-2BService-2BInstance-2Bfrom-2Ba-2BDesign-2BModel&d=DwMFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=sKhK8TCV9f5qt2EIn9P_Cbogf6J135ixB35mT6OJusY&s=XT99Ejmx2R3cKbzO42fkRrT1jBYK8fDB7MndCljNl1M&e=>...
 for Openstack Ocata - while I don't see any Ocata vs. Mitaka issues. You may 
want to check for duplicates

Mit freundlichen Grüßen / Kind regards
Josef Reisinger
When wisdom comes to call, there's nobody listening at all - Pendragon / Man Of 
Nomadic Traits

IBM Sales & Distribution, Communications Sector
Certified IT-Architect Telecommunications
IBM Certified Telecommunications Industry ITA
Lehrbeauftragter an der Hochschule Fresenius

IBM Deutschland
Godesberger Allee 127
53175 Bonn Beuel

Phone:    +49 151 1426 4559
Mobile:  +49-(0) 151 1426 4559
E-Mail:  [email protected]<mailto:[email protected]>


IBM Deutschland GmbH / Vorsitzender des Aufsichtsrats: Martin Jetter
Geschäftsführung: Martina Koederitz (Vorsitzende), Nicole Reimer, Norbert 
Janzen, Dr. Christian Keller, Ivo Koerner, Stefan Lutz
Sitz der Gesellschaft: Ehningen / Registergericht: Amtsgericht Stuttgart, HRB 
14562 / WEEE-Reg.-Nr. DE 99369940






From:        Tapan Majhi <[email protected]<mailto:[email protected]>>
To:        "[email protected]<mailto:[email protected]>" 
<[email protected]<mailto:[email protected]>>
Date:        06.07.2017 15:00
Subject:        [onap-discuss] [DOC] Documentation for running demo on 
Openstack Mitaka
Sent by:        
[email protected]<mailto:[email protected]>
________________________________



Hi All,

We managed to run the vFw and vLB demo on Mitaka version of Openstack.
Some modification in the robot script/Python libraries and the heat files of 
vFW and vLB is done to run the demo successfully.
We are thinking of creating a page in the wiki to list down all the changes .

Let me know if this will be helpful for others or not. If yes where should I 
create the page?
Possible options I can think of is  
https://wiki.onap.org/display/DW/Installing+and+Running+the+ONAP+Demos<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Installing-2Band-2BRunning-2Bthe-2BONAP-2BDemos&d=DwMFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=sKhK8TCV9f5qt2EIn9P_Cbogf6J135ixB35mT6OJusY&s=c6FjgLt_yvhnuE3Ov4MFR8YEPZYvCmdsHFMd0fXKJNg&e=>

Please suggest

Regards
Tapan M

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement, you may review at 
https://www.amdocs.com/about/email-disclaimer<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer&d=DwMFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=sKhK8TCV9f5qt2EIn9P_Cbogf6J135ixB35mT6OJusY&s=njUblPKp8zzgwiWjkCyvvyHTyyDMB-VNUHVUex2-vnY&e=>
Amdocs Development Centre India Private Limited having CIN: 
U72200PN2004PTC0188320 converted into Amdocs Development Centre India LLP (A 
limited liability partner­ship withLLP Identification Number: AAI-6901 
effective 28th Feb 2017)_______________________________________________
onap-discuss mailing list
[email protected]<mailto:[email protected]>
https://lists.onap.org/mailman/listinfo/onap-discuss<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss&d=DwMFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=sKhK8TCV9f5qt2EIn9P_Cbogf6J135ixB35mT6OJusY&s=Vp-p71WEvesKvsNtz2PWfUhIbfuiRbwybYIJGTbeKwA&e=>



This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement, you may review at 
https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>

Amdocs Development Centre India Private Limited having CIN: 
U72200PN2004PTC0188320 converted into Amdocs Development Centre India LLP (A 
limited liability partner­ship with LLP Identification Number: AAI-6901 
effective 28th Feb 2017)
_______________________________________________
onap-discuss mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-discuss

Reply via email to