MasterofProject

Foundry Iron and Foundry Cloud of those things

Label Server.netWindowsServiceAsp.netMicrosoft
1826 people read comment(3) Collection Report
Classification:

In the first part, it talked about the matters relating to the installation of micro iron foundry and micro cloud foundry, the next natural is installed iron foundry and cloud foundry, and understand familiar with both.


Requirements

First need to understand the installation of some of the conditions. The installation environment appears to be than last time, a lot of loose, there is a need to two machines (physical machine, virtual machines can be, here does not involve nested VMS and VT support. However, the author is in the virtual machine on the completion of the installation). Although the requirements of the two machines are not very strict, but the operating system of the two machines still have certain requirements. This everyone should know, Foundry Cloud installed in the Linux operating system (the author use Ubuntu 10.04), Foundry Iron installed in the Windows operating system (according to the official website, the author has tried Windows Server 2008 R2 and Server Windows 2008 SP1 R2 with server core, as for the effect, behind the talks and. The following is the installation process.


Installation

And the relationship between the two micro, iron foundry plainly just a DEA component of cloud foundry. Installation takes only the iron foundry DEA service connected to the cloud foundry can be, but need to pay attention to is, at this time of cloud foundry (by GitHub iron foundry Vcap installation, addressHttps://github.com/IronFoundry/vcapAnd before the Cloud on the GitHub Vcap Foundry (addressHttps://github.com/cloudfoundry/vcapFoundry Cloud installed in a slightly different. The former on the basis of the latter, changes a few parts, so that the former can be supported by.Net to complete some of the basic work.

In the installation process, cloud foundry (by iron foundry altered version) by laboratory Daniel seniors Lei brother completed (Sina micro Bo ID:Willow smoke pile of snow). According to senior Lei brother the, the installation is very smooth (Executive dev Dev_setup/bin/vcap_dev_setup dev setup). Unlike installation of the original cloud foundry installation that will be all kinds of weird errors occur, for example to external dependencies. After the installation is completed dev_setup/bin/vcap_dev Start to start Foundry Cloud.

Above is the cloud foundry installed, as it relates to iron foundry, before more or less certain to involve the installation of cloud foundry, for the specific operation will not repeat them.

The following is the installation process of Foundry Iron. Before in the description of the process, I first said that we VLIS Laboratory of the installation experience can be divided into three steps: 1. The first attempt to Windows Server 2008 R2 SP1 with server core mounting iron foundry, failed, the installation steps can be iron foundry, reference website blogHttp://blog.ironfoundry.org/2012/01/cloud-foundry-with-iron-foundry-windows-core-install/2 after the first defeat, try to use micro Iron foundry, by manually install iron foundry, then connect the cloud foundry, the successful; 3. In the second step of success, try using Windows Server 2008 R2 install iron foundry, then connect cloud foundry with successful results. Of course, the installation process is not smooth sailing, there are many problems, but have solved the one one.

That is followed by a detailed description of the installation of the three

Installation 1

Installation environment must be Server Windows 2008 SP1 with R2 server core. So in the installation, the first installation of Server R2 2008 server core Windows, and then install the Microsoft update program pack service 1 (SP1), more than 900 MB. If you do not know about the Windows 2008 core server, you can refer toWindows 2008 core server up and running. Subsequent execution:

Start /w ocsetup IIS-WebServerRole c:\Users\Administrator>
C:\用户\管理员>启动/ W ocsetup是netfxenvironment
C:\用户\管理员>启动/ W ocsetup IIS isapiextensions
C:\用户\管理员>启动/ W ocsetup IIS isapifilter
C:\用户\管理员>启动/ W ocsetup IIS netfxextensibility
C:\用户\管理员>启动/ W ocsetup iis-aspnet
C:\用户\管理员>启动/ W ocsetup microsoftwindowspowershell
C:\用户\管理员>启动/ W ocsetup servercore-wow64
C:\用户\管理员>启动/ W ocsetup netfx2 servercore
C:\用户\管理员>启动/ W ocsetup netfx2-servercore-wow64

将dotnetfx40_full_x86_x64_sc .exe拷贝到C:\用户\管理员目录下,执行,则安装好.NET Framework 4运行环境。下一步是在注册表中添加项以便于启动IIS远程管理服务C:\用户\管理员>注册地址hkey_local_machine /软件/微软/ Web管理/服务器/ V enableremotemanagement reg_dword / D / T 1。安装完以上内容后,重启机器。重启完毕以后,启动wmsvc,使用命令为C:\用户\管理员>启动wmsvc。接着到指定目录下安装铁铸造DEA的服务,使用命令为C:\用户\管理员> msiexec我ironfoundry。DEA。服务。64。MSI,则将该组件安装完毕。最后一步,则为启动该组件,进入目录C:\程序文件\ \ DEA执行可执行文件铁铸造。

以上操作为均为铁铸造的官方指导,其中以上步骤我们实验室均全部完成,理论上可以安装完成。但是我们的服务器核心却不能与外界通信(外界可以访问该机器,但是该机器访问不了外界),在郁闷中,我们尝试了以下安装2。


安装2

在安装1的郁闷中,我们尝试了该方法,并最后取得了该战役的胜利,着实振奋人心,哈哈。

在微铁铸造中的操作很方便,因为在查看了一番微铁铸造的文件结构以后,发现他的文件结构与铁铸造的几乎一致,所以可以将其当成是一个铸铁厂。第一步首先要做的就是卸载微铁铸造,这里肯定有人会问,为什么要卸载呢?原因是微铁铸造的连接主要是面向微云的,所以连接的很多部分都是指定的,不能更改卸载微。 铁铸造的命令为C:\用户\管理员> msiexec我ironfoundry。DEA。服务。64。MSI。将其卸载后再重新安装,因为在重新安装过程中,我们就可以指定新的natshost的IP地址了,填写其中的四项,其他的可以不填:

NAT主机:172.17。××。×××(填你自己的云控制器的IP地址)
NAT端口:4222(云的NAT默认监听端口为4222)
用户:NAT(NAT的和都可以找到用户密码,在nats_server。YML和cloud_contrller。YML中)

密码:NAT

这样的话,铸铁厂的安装就完成了,接着就应该是启动这个DEA服务来和云连接了,进入目录C:\程序文件\ \ DEA执行可执行文件铁铸造。

这样的话,理论上可以完成最终连接,但是在这过程中我们又遇到了几个问题,而且尝试了几台机子,都遇到了这个问题。以下介绍一下遇到的问题。

问题1:在连接过程中,出现一个bug,bug的描述为某个端口已被占用解决方案如下12345:

1。查看该端口端口的占用者,命令:netstat -怡安| findstr“12345”;

2。找到占用者的进程,命令:tastlist |中“端口”;

3、熟练最终使用PID命令杀死掉ironfoundry。DEA。服务。exe进程。

一旦解决了问题1,那么在命令行中就能显示,连接到172.17。***。***,这说明铁铸造已经和云连接完毕,新鲜的铁铸造DEA服务启用完毕啦,之后就等待你来净应用啦推。

理论上讲(貌似说了不少”理论上讲”了,唉,无奈,安装工程实在折腾哈),做到这一步就算完成啦,但是后面还会出现一个奇怪的问题。

问题2:In the.Net push application, the application can be stage, but in the final step start is always not successful. But in this case, the first to think of nature is to support the DEA service.Net in the end there is no connection. With this doubt, we look at the Foundry Iron (Iron Foundry micro variant version, ha ha) command line, and found that there is always a message loop unsupported "Runtime" clr40 and on the other hand iron foundry thrown their support for the operating environment display is "aspdotnet40". So, the iron foundry and cloud foundry support for the. Net runtime environment description will appear the inconsistent. In the final access to the Foundry Cloud source code, found the followingCloud Runtime Foundry support:

Aspdotnet40:
Description: "ASP.NET 4 (obsolete)"
4.0.30319 version:
Clr40:
.NET "CLR description: 4"
4.0.30319 version:
Clr20:
.NET "CLR description: 2"
2.0.50727 version:
Visible aspdotnet40 has been eliminated, and now used is clr40. Can see the aspdotnet.yml file to see:

-
Aspdotnet "name"
Runtimes:
- "aspdotnet40":
4.0.30319 "version"
ASP.NET "description: 4"
- "clr40":
4.0.30319 "version"
.NET "CLR description: 4"
True default:
- "clr20":
2.0.50727 "version"
.NET "CLR description: 2"
App_servers:
- "iis":
Internet "Information Services description"
False executable:
True default:
Detection:
"Web.config": true web.config must be present #
Staged_services:
# vim: filetype=yaml
Manually change the runtime part to
Runtimes:
- "aspdotnet40":
4.0.30319 "version"
ASP.NET "description: 4"
Default:true
- "clr40":
4.0.30319 "version"
.NET "CLR description: 4"
      False default:
- "clr20":
2.0.50727 "version"
.NET "CLR description: 2"
Default:false

After the modification is completed, the.Net push application can be completed push. Bingo, ha ha, there is no feeling of dense willow trees and bright flowers? If you try it, do this step, there will be a feeling of.

This application is still in the same as the last blog post, for a simple World Hello and the application of the link, the following linkHttp://code.msdn.microsoft.com/windowsazure/Windows-Azure-HelloWorld-ee52983e.

Here, I think it is necessary to give a brief introduction, willThe reason for the problem 2. We feel that which may be because cloud foundry update very frequently, resulting in a lot of configuration file changes; and iron foundry is no cloud foundry updated less frequently, because of. Net development environment or immature, update is not enough to catch up with cloud foundry, so in problems 2, but iron Foundry should be able to support a previous version of Foundry Cloud. I consulted Foundry Iron on this issue.Bakken LukeSir, he replied as follows:

Hongliang -
Are correct. You I am in the process of doing some work on the.NET DEA and it only understands aspdotnet40 right now..
Can also specify You a runtime with the VMC command from the vmc-IronFoundry gem: ""
Push myappname --path C:\proj\myapp --runtime VMC aspdotnet40


Installation 3

The third installation process is relatively simple, because there are second successful installation experience. This time is mainly to test whether the server Windows 2008 R2 can also be successfully installed, the result is satisfactory. The installation steps in the front and the Installation1 are consistent, but none of these four steps, because it is not in the core server mode:

Start /w ocsetup MicrosoftWindowsPowerShell c:\Users\Administrator>
Start /w ocsetup ServerCore-WOW64 c:\Users\Administrator>
Start /w ocsetup NetFx2-ServerCore c:\Users\Administrator>
Start /w ocsetup NetFx2-ServerCore-WOW64 c:\Users\Administrator>

After the completion of the operation of Installation 1, according to Installation 3 to operate, will encounter the same problem 1 and problem 2, and then the solution is also consistent, until the final.Net successful push application.


In this way, Foundry Cloud and Foundry Iron on the communication problem is solved, and we hope to be useful to everyone.

At last, I will use that sentence again.


It and feel the love. Do







top
Zero
step on
Zero
Guess you're looking for
View comments
* the above user comments only represent their personal views, does not represent the views or position of the CSDN website
    personal data
    • Visit84370 times
    • Integral:One thousand three hundred and fifty-four
    • Grade
    • Rank:18446th name
    • Original47
    • Reproduced:0
    • Translation:1
    • Comments:50
    Blog column
    Contact information
    Latest comments
hammocksuite.co