Hi KriJay, I think that you should use image with password auth on console. You cannot choose ssh keypair for service instance and standard cloud images have configured only eth0 interface as active dhcp. I suggest to boot normal fedora, configure password for root, prepare eth1 as boot dhcp and after try to run service instance.
Jakub <http://tcpcloud.eu> ________________________________ Odesílate: Users [[email protected]] za uživatele KriJay [[email protected]] Odesláno: 7. srpna 2015 00:09 Komu: [email protected] Předmět: [Users] Service Instance - Interface issue - Fedora 22 Hi List, I have installed latest Ubuntu 14.04 + Icehouse<https://webdownload.juniper.net/swdl/dl/secure/site/1/record/59248.html> version on Ubuntu 14.04. Openstack and Contrail are up and running successfully. I want to create a basic service chaining (L3 service) and I have created service template with InNewtork and Firewall as attributes. I want to replicate the following architecture [Inline image 1] Created Networks and Service Policy and launched cust-vms in openstack successfully. Issue - I have launched Service Instance with two interfaces one with cust-left-network and one with cust-right-network. This service instance is available in Openstack Horizon dashboard but only one interface is up and that one gets cust-left network ip address i.e 192.168.0.4 Second Interface eth1 is down and it does not get the cust-right network ip address. Pain point is that I can not login to the fedora image as it requires to setup a keypair. After we launch a service instance in contrail we can not assign keypair to that instance in openstack via Horizon dashboard. Is this a known issue? If not am i doing some thing weired? any guidance will be great help. Thanks, Jayaram Nori
_______________________________________________ Users mailing list [email protected] http://lists.opencontrail.org/mailman/listinfo/users_lists.opencontrail.org
