اهلا وسهلا بك فى بوابة الثانوية العامة ... سجل الان

العودة   بوابة الثانوية العامة المصرية > القسم الإداري > أرشيف المنتدى

أرشيف المنتدى هنا نقل الموضوعات المكررة والروابط التى لا تعمل

 
 
أدوات الموضوع ابحث في الموضوع انواع عرض الموضوع
  #1  
قديم 25-09-2010, 09:25 AM
klmn755
ضيف
 
المشاركات: n/a
Smile Why WOW level machine images don’t

The standard method of operation in the virtualization world is to work with machine imagesWOW Gold sale. This translates to: launch a server with an image that is “close” to what you want, then log in and install the software you need plus make any comfit changes, then create an image from that server for WOW level. Later on, when you need an instance of that serverKaufen WOW Gold, you launch the image and hopefully it comes up ready to go. While this process may sound simple, it’s actually anything but that and takes quite some time. I went through the bundling treadmill back in 2006 and concluded this wasn’t productive. The reasons are simple:Images are too monolithicFinal Fantasy Gil. Everything on a server is bundled up in one image file which makes it difficult to manage a collection of imagesRuneScape Gold. Change the version of one software package you commonly use and you has to recreate all images that happen to use that package. This quickly gets out of hand. Images are opaque. From the outside it’s hard to tell what’s in an image. Even if you fire it up it’s not convenient to poke around to figure out what’s installed and how it’s configured. Try determining the difference between two WOW levelimages: not a pleasant task.Images are too big. They are unwieldy to work with. Take two images of different versions of your app server. More than 90% of the bits are typically identical, (often more than 99%). But finding the interesting ones that differ is like finding a needle in a haystack. This is ridiculous and contributes to making images hard to work with. Images are too static. You can’t fully configure each server. When you launch the 10th app server it needs to know its number 10 and not 9. When you launch a test app server it needs to know it’s in a test deployment (e.g., don’t send alert emails to the ops team), yet you want the same image to be used in test as in production, otherwise, what are you really testing? So you need some dynamic configuration mechanism to “personalize” each server at boot timeWOW Gold.
 

العلامات المرجعية


ضوابط المشاركة
لا تستطيع إضافة مواضيع جديدة
لا تستطيع الرد على المواضيع
لا يمكنك اضافة مرفقات
لا يمكنك تعديل مشاركاتك

BB code متاحة
كود [IMG] متاحة
كود HTML معطلة

الانتقال السريع


جميع الأوقات بتوقيت GMT +2. الساعة الآن 02:50 AM.