I'm trying to setup a non-dev Corda network, I have seen document from:
https://docs.corda.r3.com/setting-up-a-corda-network.html
However, it trust is a test network, so anyone can tell me how to setup the non-dev network for utilizing in real life?
Thank you.
The process for creating your own non-dev network is documented here: https://docs.corda.net/head/permissioning.html#creating-your-own-compatibility-zone.
Related
I am trying to deploy a 5G network using open-source software. I ran into an issue that seems to have nothing on it. When I try to instantiate a Network Service, it says that it cannot find the K8s cluster that meet the following requirements: {}.
This is how it actually looks:
No k8scluster with requirements='{}' at vim_account=34510160-24e6-4c6a-93ec-787d00a2518a found for member_vnf_index=oai_cn5g_amf
The VIM account is simply the Openstack server. Do you guys know how to link a kubernetes cluster in Openstack?
Thanks,
Taylor
I'm trying to forward requests from a compute engine instance to an internal API (its an on-premise API that communicates to the VM through Cloud VPN) but without luck, I tried to research how to accomplish this, but with no results.
Someone knows how to achieve it?. In short my goal is to access the on-premise API from my local computer for development purpose using the CE as a proxy.
I am open to create more resources or to change the CE instance if there its a better way to handling this.
My VM is a simple Debian 10 machine.
As John Hanley commented. You can accomplish this by doing SSH tunneling using the CE instance as the middle man.
A good tutorial to follow is this one, which is from the GCP community itself.
how to setup multiple provider network in openstack packstack. I'm deploying on single server with 4 port nic physical. The setup as below
port1 (eth0) = provider1 = 192.168.10.0/24
port2 (eth1) = provider2 = 192.168.20.0/24
port3 (eth2) = provider3 = 192.168.30.0/24
port4 (eth3) = provider4 = 192.168.40.0/24
As what I understand 1st I need to create ovs bridge and add map to each port. Got others steps such as L3 agent configuration, ML2 plugin and ovs agent which not really clear how to do about it. As I deploying using packstack and got packstack answerfile that can be customized. I have done with single interface port in packstack file but when need to add multiple nic port, I'm not sure which part should I add/change.
If someone had done this using packstack answer file please share how it can be done. Thank you for all you support and help.
If openstack already deployed can it be changed to fulfill the requirement above? or clean deployment?
This is parameters answer file which I'm not sure if this is valid as per my requirement. I may wrong and need advise and confirmation below.
CONFIG_NEUTRON_L3_EXT_BRIDGE=provider
CONFIG_NEUTRON_ML2_TYPE_DRIVERS=vlan,flat
CONFIG_NEUTRON_ML2_FLAT_NETWORKS=*
CONFIG_NEUTRON_OVS_BRIDGE_MAPPINGS=physnet0:br-eth0,physnet1:br-eth1,physnet2:br-eth2,physnet3:br-eth3
CONFIG_NEUTRON_OVS_BRIDGE_IFACES=br-eth0:eth0,br-eth1:eth1,br-eth2:eth2,br-eth3:eth3
CONFIG_NEUTRON_OVS_BRIDGES_COMPUTE=br-eth0,br-eth1,br-eth2,br-eth3
CONFIG_NEUTRON_OVS_EXTERNAL_PHYSNET=physnet0,physnet1,physnet2,physnet3
Pls advise if this config is good for the requirement. Thank you
I managed to get it works as follows:-
1. create new ovs bridge for each ports
2. mapping ovs bridge
3. restart neutron
4. create new provider network
Thank you.
Kubernetes supports OpenStack as cloudprovider (/pkg/cloudprovider/providers/openstack).
However, it seems there is no equivalent support for a OpenStack-provider to setup a cluster on an on-prem OpenStack environment via "./cluster/kube-up.sh" (supposed to be located in cluster/$IAAS_NAME).
Is my understanding correct?
If so, would there be any impediments to create such a provider as contribution? (assuming to fulfil the requirements for such provider)
I'm sure the kubernetes project would welcome such a contribution.
The main impediments are dealing with the fact that on-prem setups are more varied than cloud-provider-based setups, and with testing of the code you contribute.
I am fairly new to the NFV+SDN. I have downloaded the OpenDayLight and OpenStack in one Fedora 20 VM. I have mininet network as underlying physical topology in a separate VM. I want to run services like VPN, L3 routing and NAT, Loadbalancing etc on OpenStack, but I don't have a very clear image on how to start. As far as I have understood I have to run these services on OpenStack nodes (through VM instances) and route the traffic through mininet topology with OpenDayLight as the controller in the middle.
My confusions are:
How to start writing the applications (Firewall, VPN, NAT, etc) on OpenStack?
Do I have to write a code for such services or is it command line configuration?
I came across Neutron API, Is that of any help?
Came across this: http://docs.openstack.org/api/openstack-network/2.0/content/API_extensions.html
I have looked at the other questions regarding writing "Hello World" on OpenStack but could not find anything. I shall be grateful to you for any information that could get me started on this project.
I would suggest you to check OpenBaton.
Nowadays I'm working with it which can be used NFV MANO. In addition it's ETSI compliant and their solutions are easy to implement and configure.
For your confusions- You do NOT need to write code explicitly for Firewall / VPN / LB. You need to configure the Openstack Neutron to allow these services directly. The code is already present. You need to configure them to use them. For NAT there is L3 agent already running in the default setup ( al least via packstack )
Neutron API is of any use??? I assume you are refering to REST API and NOT CLI.
Well everything that you do on Dashboard is actualy represented as a REST API to Neutron Server ( not just Neutron but all the other components of Openstack ). All the components of Openstack ( Neutron, Nova, Glance, Keystone, etc ) interact via REST API with each other and RPC mechanism within each component. All the clicks on the Dashboard are actually thrown as a REST API call to the component servers!