Skip to main content

Posts

Accessing OCI public services via private network

Introduction When you running your workloads on any public cloud, protecting your network, data, instance from prying eyes and hands is one of the most important things. But whenever you need to access public services offered by a cloud, one has to go through the internet. When your data is going through the internet, your network/instance(if not using NAT) and data are exposed to the public. Is there a way to access public services offered by a public cloud safely, securely and with the same performance and high availability? So if you are using Oracle Cloud Infrastructure(OCI), look no further, your answer is Service Access Gateway(SGW). OCI users can access all these services directly from their Virtual Cloud Network(VCN) with private Subnet without any NAT, IGW by using SGW(No need to go to the internet). All traffic for these services is routed through OCI's internal network, thus protecting your data/network/instance. How to set up an SGW? This section explains
Recent posts

Introduction to SoftLayer/IBM's Cloud Load Balancer.

IBM Cloud Load Balancer(CLB) Introduction. They have couple of other LBaaS services but here we are going talk to about the Cloud Load Balancers. IBM introduced a new Cloud Load Balancer, which is equal to Amazons AWS (elasticity, ssl termination and L7/Application load balancing, auto recovery etc etc). All these in one LBaaS unlike AWS. IBM CLB offers couple of variations which user can apply at the time of CLB creation. For e.g. Select which data center one wants to create the CLB in. User can select a private CLB or Public CLB. Public CLB can be reached from the public networks where as private CLB can only reached within ones private network.  For Public CLB one can select which public VLAN one can use. There is an option to use the IBMs public VLAN where customer doesn't have any control or user can select to get the public VAN from their own account, where customer have absolute control over it. Which private VLAN to use. Customize CIPHER for SSL HTTPS support

PART 1: How to use SoftLayer Python library.

Install the SoftLayer's Python library.  pip install softlayer or clone the source code from the github and install from source code. git clone https://github.com/softlayer/softlayer-python.git python setup.py install Once we have installed the SoftLayer Python library we are ready to use it as shown in the following example. You need your username and api key to run the below example. One can get both user name and api key at the following link once you login successfully. https://control.softlayer.com/account/user/profile Accounts username and API key E.g. showing how to use SoftLayer Python library. import SoftLayer from SoftLayer.managers.image import ImageManager client = SoftLayer.Client(username='', api_key='') image_manager = ImageManager(client) mask = "mask[id,name,note]" imageTemplates = image_manager.list_private_images(mask='id,name,note') print("ID - Name - Note") for template in imageTem

Enable stats GUI on haproxy.

Add bottom snippet to the haproxy.conf below the defaults section. listen  stats         bind 19.41.259.10:1234         mode            http         log             global         maxconn 10         clitimeout      100s         srvtimeout      100s         contimeout      100s         timeout queue   100s         stats enable         stats hide-version         stats refresh 30s         stats show-node         stats auth admin:password         stats uri  /haproxy?stats Make sure you are updating the IP address on the bind to your VIP and if you want, you can change the port also. One can even change the uri on the last line of the above snippet, like stats uri /haproxy_stats or whatever one wants. To make sure you have not done any mistake in the config file, one can use the following command to validate. haproxy -c -f haproxy.cfg Once everything looks good, restart the haproxy process and stats GUI should be available at 19.41.259.10:1234/hapro

How to enable Openstack Octavia, LBaaS V2 with devstack.

Little Intro to Octavia. Octavia is a service manager for Openstack Load balancer as a service. Neutron LBaaS V2 plugin talks to Octavia through Octavia driver. Octavia driver talks to Octavia api(o-api) and that in turn talks to Octavia control worker(o-cw). Neutron LBaaS V2 Plugin ----> Octavia plugin driver -----> o-api ----> o-cw Other than o-api and o-cw Octavia has 2 more components, housekeeping(o-hk) and health manager(o-hm). o-api Octavia api server which receives all the request from octavia LBaaS driver and passes it to o-cw. o-cw It's the main workhorse, it creates the load balancer VMs( amphorae ), configures them. o-hk keeps track of spare amphorae. o-hm Manages the health of the amphorae through heartbeats, collects the stats and takes care of fail over by creating a new amphora when it fails to get the heartbeat. How to enable Openstack Octavia, LBaaS V2 with Devstack. Since octavia uses a VM for loadbalancer its needs good a

Adding a table to the openstack databases using migration scripts

So I had a task of adding a new table to the neutron database and at the same time not to use the neutron's migration script, as we wanted to keep the neutron code pure. I tried to google for the alembic data migration but could not find anything useful. So I started to reverse engineer the migration scripts of the other Openstack projects. I used the db code base from the following link. https://github.com/stackforge/group-based-policy/tree/stable/juno/gbpservice/neutron/db So I ll just mention the modifications we need to do to make it work. Please note that I am doing these changes in the Devstack environment. 1. Create folders for new project. Lets say we are building a new project called test_db. Add a folder named test_db as shown in the below location /opt/stack/test_db/test_db/ (Yes 2 folders just to keep in sync with Devstack Arch) 2. Copy migration folder from the below link to  /opt/stack/test_db/test_db/ https://github.com/stackforge/group-based-policy/t

The complete review of the LG's watch and Android Gear.

Its been like 2 weeks since I got a LG's G watch. So here I go with all of the good, bad and ugly things about the LG's G watch and Android Grear. So first lets go over the specs. OS                    Android Wear (Compatible with Android 4.3+) STRAP            22mm (0.86inch) Changeable Watch Strap SCREEN            1.65” IPS LCD DIMENSIONS   37.9x46.5x9.95 mm BATTERY    400 mAh PROCESSING   Qualcomm® Snapdragon™ 400 processor with 1.2GHz CPU MEMORY    512 MB / 4 GB SENSORS    9 Axis (Accelerometer/Compass/Gyro) So why g watch instead of samsung. 1. It was a gift so .... but even if I wanted to buy I would have got g watch instead of samsung's. 2. 400 mAh of battery compared to 300 of samsungs. 3. LCD screen, dont think I am crazy, its a small watch and I think one doesn't need a high res screen which eats up more power. 4. Read and watched loads of reviews, where everyone was talking about how comfortable it is to wear all day compared