Category Archives: Uncategorized

Migrating your WordPress blog to GoDaddy – part 1

[e1: Updated on 23 Feb 2015. I had to repeat the entire process! The Nameserver was pointing to the old hosting provider]

I had to migrate my blog from the current provider it went down several times. I chose GoDaddy as my domain is also registered with them. Because my blog is based on WordPress, I chose the WordPress package. GoDaddy provides a migration tool, which makes the process much easier. There are still things to prepare.

GoDaddy will need an FTP site, user and password. The problem is the Path value. As you can see from the screenshot below, the value has to be Undefined. That actually means the “root” directory. I did not know that, and GoDaddy Support did not provide advice that it had to be at the top directory. I had to create a new ID, as the existing ID has a password that I do not know. In the directory field, type “/”, and this would set it to root directory. [23 Feb update: I could have modified the password of the existing ID. There is no need to create a new ID]

0 site migration

You also need to know your WordPress admin. The screenshot below shows that.

0 site migration 1

Once you did the above, you are ready to migrate. You click the Migrate choice.

1 site migration

It will take you to the screenshot below, where you fill it with the info that you’ve prepared earlier. Notice that GoDaddy provides you with a temporary host name, which is great.

2 site migration

Clicking the submit button will get you the screenshot below.

3 site migration

If you check with the All Hosting Accounts page, it will show you that your site is being updated.

4 site migration

You then get the status below. If your site is pretty small, this is done within the 30 minutes.

5 site migration

You can actually check what it looks like. This is what it looks like before it’s updated

6 site migration

And… after it’s updated! So it’s basically all copied! Thank you GoDaddy!

7 site migration

Now, because of the temporary address, I need to migrate the hostname too. This is not easily shown in the migration wizard. If you do not do this step, the domain is not associated with the migrated content. Click the “Add Domain” button.

8 site migration

Since my domain is with GoDaddy, I can easily just choose from a drop down.

9 site migration

Once you submit, you can see that the status is now reflected, as you can see below:

9 site migration - 1

I gave it around 1-2 hours, and it’s done!

9 site migration - 2

This is much easier and a lot less scary than what I thought 🙂

23 Feb 2015 update

…. and that was the beginning of my nightmare. Little did I know that the DNS is still pointing to This is because the Name Servers are not modified by GoDaddy migration tool. The tool does not inform that you need to do it. Please read this for details.

The Chef and his cooking – Story of VMware Admin

I see a lot of VMware Admin/Engineers/Architect at end-user environment do not extend his/her influence beyond architecture. I think that’s a lost opportunity because Operations and Architecture are like Yin and Yang. Or Mobius strip.

I shared the idea that as the creator of the platform, we have to have interest on how it’s operated. It was an impromptu presentation at our VMUG Singapore back in mid 2014, hence no slide.

I used analogy about restaurant.

The restaurant business provides a good analogy to our Infra-as-a-Service business. We (Virtualisation Architect/Engineer/Admin) are the Chef. In that end-user environment where you work, you are the expert in producing what your customers want. You architect and design a solid platform, where your customers can confidently run their VMs. If there is an issue, you often get involved, restoring their confidence in your creation. You are seen as the VMware guy, or the virtualization expert. Yes, you may engage VMware PSO or SI, but they are not working for the company. You are the employee. As far as your customers concern, the buck stops at you.

You do not sell hardware nor software. You charge your customers per VM. In fact, to ensure that your customers order the right kind of VM, you need to charge per vCPU, per vRAM and per vDisk. The chargeback model is something that I very rarely see we discuss. We tend to stay in technical discussion. We need to realise we are no longer just a System Builder. We are Service Provider. By not extending our circle of influence into how App Team should pay for our service, we created the issue we have today (Oversized VM, dormant VM, VM sprawl). We need to “step out from the kitchen” from time to time. We need to be like Chef who step out to the dining area, building relationship with his customers, explaining the reason behind his cooking.

As the Architect/Engineer, we are the best person to determine how much it should be charged. We build this thing. We know the costs, and we know the capacity. Not convinced? Put it this way, would you rather someone else determine how much your creation is worth?

We all know that IT exists because of Business. It starts with the Business. Some of the issues we have are caused by unsuitable chargeback model and incorrect Service Tiering. The VM in Tier 1 (mission critical) platform cannot cost the same with the VM in Tier 3 (non prod). I’d make sure there is distinct difference in quality between Tier 1, Tier 2 and Tier 3, so it’s easy for business to choose. Need a good example? Review this.

Using the restaurant analogy, say you cook fried rice. It’s your dish. You need to determine the price of the fried rice. You also need to be able to justify why you have normal fried rice and special fried rice, and why the special one costs a lot more for the same amount.

To me, the Chargeback model and the Service Tiering serve as Key Drivers to our Architecture. I will not consider my architecture complete unless I include these 2 in my design. We are architecting to meet the business requirements, which are “defined” in the chargeback model (e.g. the business wants a $100 VM per month, not a $100K VM per month), and service tiering (e.g. the business wants 99.999% and 3% CPU Contention).

As shared, I see a chance for us to STEP UP and STEP OUT.

Step out of the kitchen and network with your customers (the App team). Educate and fix the problem at the source. Step up from pure IT architecture to business architecture. Architect your pricing strategy and service tiering.

The good thing about pricing is…. your benchmark is already set.

Azure, AWS, Google, and many SP have to a certain set the benchmark. Your private cloud cannot be too far from it. Too low and you will likely make a loss (it’s almost impossible to beat their efficiency). Too high and you will get a complain. Another source of benchmark is physical.

If you are pricing your VDI, the cost of a PC sets your benchmark. You can be higher, but not by a huge gap. A PC costs $800 with Windows + 3 year warranty + 17” monitor. Add your IT Desktop cost, and you meet your benchmark

Hope the above provides clarity. I’m keen to hear your thought.