Translate

Monday, 19 June 2017

Docker EE for AWS

Somehow, I struggled through Docker. I will outline my steps so that you don't have to follow the tedious path.

First I tried to install Docker on Windows.

Pitfalls: OS version. If you don't have the Windows 10 Pro edition, you can use the Docker toolbox only.

So, okay. Download the Docker toolbox.

And I checked the VirtualBox option for good measure and it did stand me in good stead because - believe this - the Windows Server image on the EC2 instance cannot have its Hyper-V/AMD something started because you can set the setting only in BIOS and on the EC2 instance, running on Remote Desktop (RDP), there is no way of accessing the BIOS, even if it made sense!

Below is the roadmap of the 1st attempt





Initially, I thought like this:                                                          Then, I thought like this:






                                          






No, the above is not a joke. It is the situation one finds in when such thoughts get expressed. It is in this predicament, like in the House MD serial when Dr. House gets his solutions through differential diagnosis, that I discovered this and inserted the below like they insert mesages in captions of social media posts, shares and ads. In any case, my readers do not seem to be human so this might just serve as a reference point!

A joke is when a nutcase from Pondicherry, it seems, holds up many cars because it wants to hire someone! As if it were a Shahrukh Kan trying to hire Sachin Tendulkar or some super influential rich pot pitching for a great rock star! And the actual joke is because of some equally well-nutted nutcases, who first could not understand why Google offered its search services for free and then could not understand why we worked on Open Source projects for free and now cannot understand how Test Driven Development could be if no code exists and so, they want to jam their foot in the door with the justification that the nutcase, without hiring you or without even having a company, (it is all future, you know, and it is based on the fact that the message that it is hiring a person without hiring a person (and believe it, many well-established HR managers know this for a fact but instead of taking direct action through the police, they resort to giving symbolic messages like saying "You are hired" without sending the offer/appointment letter!

One nutcase 'inspiring' many nutcases in the region!) is supposed to make you think that the nutcase is actually asking for its own company or house or political party (something like a ransom!) ie, it is something like TDD, hiring without hiring or even having a job opening or even without a company and that they are testing the 'system' - the governance and the police, as in Test Driven 'Development', and since the media is pretty stupid, it would get blamed on the opposition party! And as in tests, if anybody finds their ways, then there is a punishment clause - the retards who know such crazy goings-on are made to act like judges and pronounce 'Right or wrong' and accordingly, some creeps would bother you at nights, make disturbing noises over your head all night from the house upstairs and for which they create excuses to put such people as tenants in the houses, to the extent of getting admission in colleges where the creeps would have no qualifications to study.

These are nutcases because, because of such obese, narrow-minded retards wanting to know who Bill Gates is before they buy a personal computer, other retarded elements are encouraged to get into their retarded acts, that is causing major problems in the world today.


2nd attempt

I went into the VM using the RDP and started the VirtualBox and gave Ubuntu as the image. Great! It started the VirtualBox but the EC2 instance had only 1 GB RAM and the VirtualBox script wanted 2 GB, by default!

Okay! Let me check if an EC2 instance with a Linux Ubuntu image (AMI) was available. It was but I did not want to get into the Linux OS shell.

So, what is the alternative?


Docker EE for AWS



A native AWS stack that could host a Docker container on a kernel all its own, with a set of Docker engines. No underlying OS but on top of the AWS IaaS services!




Sounds great but you really cannot see it working because when you try to access the public DNS via a browser, an Apache server message will greet you that the url you are looking for cannot be reached although the server is okay!


Docker EE for AWS is a one click template to quickly deploy Docker on Amazon EC2, says the Docker EE Store. And it is, if only the template stayed put in its AWS region. It seems that the tricky part has not been documented.
The KeyPair that the template requires must be an EC2 generated Keypair from the same region in which your EC2 instance is!


Finally, the aws CloudFormation Stack gets created.












You can use this in your Docker EE deployment to AWS

Friday, 16 June 2017

Bitnami, WordPress and the AWS - a good rack

I just had to blog this - it is about my new blog on WordPress.



I had moved to Azure from AWS in 2013-14 not because I had anything against AWS or for Azure but simply because clients who wanted to use Microsoft ASP.Net and SQL Server made Azure the natural choice.

But it seems that the instances of Windows Server on AWS are more than that in Azure. The AWS has expanded like the Elastic Beanstalk with DevOps and Big Data capabilities and IoT.

At an estimated monthly cost of $5-6, AWS does offer some cool stuf.

One thing though. Why are the regions active in this menu



when an instance created in a specific region cannot be moved by the selection of a different region from the drop-down menu?

Bitnami on the Cloud with a Launchpad for WordPress is a revelation. Cool integration with aws and it even offers WAMP and other xamp stacks.

And yes, my WordPress blog on the cloud, not yet there, content-wise but it is seo enabled etc!

Thursday, 18 May 2017

There is something about Scrum - 3

...that makes me often think if there is no way that you can avoid corruption in the professional world because so bound is everything together that the more you try to resolve dependencies, the more they crop up in another form, in another aspect or place.

Productivity

Velocity, that you often hear trumpeted in Scrum, can be quite misleading.

Velocity, in common terms, means distance traveled over time. But the distance needs point A from where the calculation of speed begins, and point B,


where the calculation ends.

Velocity, in Scrum, is calculated by the number of features/tasks/stories/bugs completed/delivered/fixed by a Sprint member over a given period of time.

More specifically, in the Scrum context, the points associated with a Story - in Agile parlance, a User Story can have some points associated with it as an estimate of effort - are added up for each successfully delivered story and the sum is the velocity achieved for a sprint or a timebox. Velocity is a paraphrase, or an euphemism, for Productivity.

Productivity needs two parameters, too - one, time (usually called planned or scheduled) and two, money (usually called budgeted or allocated) - and as in matters of relativity (!), needs a surface ie., resources (usually called resources allocated).

The below image depicts all the data that is needed to measure productivity.



But, the picture although tells a lot still does not bring to light the need to measure productivity ie., a platform from which future planning, additional productivity improvements steps can be taken.

And, we also have the assignment of the resource - two resources are assigned to a task at 60 and 50% respectively and the formula (G12+G13) that has calculated shows (in the top left of the below image) that both the values have been taken into account to calculate the planned date.


Productivity is a dangerous metric to use or measure unless it is done in a mature environment and around maturer sets of people. Discussed or analyzed, especially on the internet where the amalgamation is made of disparities and varied cultures, the metric will fail to convince due also to relative application of local work culture and employee engagement parameters.

In conclusion, productivity in Scrum can be measured if the following is true:

1. All Scrum members do not take any leave during sprint (s)
2. All Sprint members are equally skilled and experienced (difficult to achieve)
3. All Sprint members are co-located.

Tuesday, 16 May 2017

There is something about Scrum - 2

...that makes me often think if there is no way that you can avoid corruption in the professional world because so bound is everything together that the more you try to resolve dependencies, the more they crop up in another form, in another aspect or place.

But there is a way to ensure that you do not allow for crafty resource developers or managers or any smart alec from messing with your Sprint plan.

Like so.



Once you set the week of Sprint (2nd column from the left, highlighted with values 1,2,3,4 signifying the week), a Sprint team member will work on on a particular task, you can restrict any work done outside of the planned weeks for the task, as shown above.

Although the Work done will show 8 hours of work done but the effort remaining part will still show the remaining 2 hours because the work was done outside of week 1 - 4 !

And if you draw a productivity chart, per team member, as per their allocated hours on a project / product team then you can track the difference of 1 or 2 hour(s) that was done outside the plan!

But, of course, as long as it is done within the Sprint, it does not make much difference but it does help you put the 'corrupt' manipulators in place ! :)


#ScrumPlanner