想法#3-科研、时代、人物

When you try to install Open Source Mano on your Google Cloud Virtual Machine Instance following the Guide on OSM Wiki, you might met the problem of accessing UI, which is running in SO container and only has an local IP to access.

Since Open Source Mano THREE apply the new authentication mechanism, you could not access the login page for UI. The detailed reason is explained in the Wiki:

Please note that in OSM 3, authentication is performed using OpenIDConnect and OAuth2.0.
An identity provider has been added to the platform and provided as a service in the SO container running on port 8009.
This means both the browser and the UI server components (that run on the SO container) need to be able to access the SO container using identical URIs.
In short, the tuple of scheme://location:port needs to be reachable via both the browser accessing the system and the UI server running on the SO container (e.g. https://10.66.202.206:8009 for a sample deployment).
This means that if your SO container is behind a NAT that cannot reach the public address of the host, authentication and authorization will not be possible and you will not be able to proceed using the UI.

To by pass this problem, the principle is make your local machine be able to access the network created by lxd on your Google Cloud Host.

There are multiple ways to do that:

Using Google Cloud VPN
- Good choice but might be overkilled, if you just have a laptop as your local machine.
Setting up a VPN server on your Google Cloud Host
- Not Elegant, but simple and easy to achieve
  - To set up an OpenVPN server and use your local machine to access it, check this post.

Then you are good to login the UI.

I think this is a bug of OSM-THREE and hope they will fix it soon and then this post will finish its job and retired.

VIEW THE POST >>

想法#2

2018-04-05

看到今年学生会对于学代会的流程和通知都非常重视的了.

大概就是去年的运动直接结果吧.

这说明有的看似毫无直接结果的运动总是会能够产生一些深远的影响的. 而如果这些运动不断发生, 影响不断累积, 那也必然会产生质变从而获得一些进步吧.

可是这样的状态又能持续多久呢? 一旦效果获得了显现, 随着诉求的不同, 运动的频率和烈度也就会下降了. 这时候如果要保持原来的状态就非常困难了. 这大概就是所谓遗失了初心吧.

所以说总是要强调

不忘初心, 牢记使命.

都是很有道理的了. more >>

VIEW THE POST >>

CN2 and VPS

2018-03-25

Just find an interesting up-to-date talking about CN2 of China Telecom and How to choose your VPS provider.

Click Here to read the post.

看到一个一篇非常新的介绍中国电信CN2线路的文章，特分享一下。

VIEW THE POST >>

Elon Musk在SXSW上的讲话

2018-03-20

前两天看到Elon Musk在SXSW上的讲话，引用部分如下：

Life cannot just be about solving one miserable problem after another. That cannot be the only thing. They need to be things that inspire you, that make you glad to wake up in the morning and be part of humanity.

Elon Musk其人，六年前是极度轻视的。认为他想法过于保守，又自诩为理想主义者。然而六年过去了，大概自己成为了保守主义者，居然又开始崇敬起他来。

或者换句话说，六年前太过于幼稚，没有看到差距在哪里，而现在大概是发现了。

VIEW THE POST >>

想法

2018-03-13

这次将网站从WordPress迁移到Hexo的时候，顺手一并把以前的中二文字给删除了，想着是希望给HR们留下一个好印象。然后最近可能RSS又被很多大佬给订阅了，讲道理这种瞎写的东西显然不适合继续发在这个地方。可是考虑到弄个公众号还是麻烦，而且我也从来不会去看我的Reeder里面的没一个未读消息，所以暂且就还是放在这里了。

我其实也不知道我写不写的完这篇文字，考虑到中文写作水平一年不如一年，前两天抽空想写点什么，结果也就继续躺在了草稿箱里，如果这篇文字最后写完了的话，看来这东西运气还是不错的，或者也许是我个人努力了一把…

more >>

VIEW THE POST >>

微信上的那些公众号

2018-02-16

虽然一直知道很多公众号是拿钱办事或者为钱办事，但总觉得那几个业内著名公众号也许会为了自己未来钱途总会对自己的内容有所把关。直到近来目睹了如何将一个口胡出来的排行榜推上各大著名科技公众号的主推内容里，才恍然大悟为何这么多公众号能够每天发布一些看起来非常有道理的所谓干货。

痛定思痛，立马取关，新的一年，安静的自我学习 =-= 提升自我

乖巧.jpg

VIEW THE POST >>

How to Create Git Submodule Repo on Server

2018-02-11

When I set up this website, I find I need to have some nested git repo hierarchy. For example, the theme always has an individual repo and I also put the entire hexo website in a git repo. To make this hierarchy more manageable, it is a good practice to add sub git repo as submodules.

If you are using git server such as github, then you are set by simply typing the commands to set up two git repo and push to remote server and then use

1	git submodule add ./dir/to/submodule

to put everything not ignored to the server.

However, if you are using a git server set up by yourself, you may wonder how you should set the remote URLs for the main git repo and submodule git repo.

Instead of create two git repos in same directory to make the two repos for main and submodule are in the same level on server, we should create the server repos nested.

For example, if our main git repo named main, and our submodule repo named submodule, then we might need to perform the following actions and get the following hierarchies.

On Server:

# go to needed dir
cd /dir/to/remote/server 
# init main repo on server
git init --bare main.git 
# get into main.git
cd main.git 
# init submodule repo on server
git init --bare submodule.git

On Local Machine with initial or developed codes:

# get into directory and create file
cd main & touch readme.md
# init git repo locally
git init
# add remote repo
git remote add origin git@yourserver:/dir/to/remote/server/main.git 
# add modified file
git add readme.md
# commit first change
git commit -m "first commit"
# push change to remote server
git push origin master
# create local nested repo for submodule usage
mkdir submodule	
# create nested repo dir for submodule usage
cd submodule & touch readme.md
# init nested repo for submodule usage
git init
# add remote
git remote add origin git@yourserver:/dir/to/remote/server/main.git/submodule.git 
# modify file
git add readme.md	
# commit first modification in submodule
git commit -m "first submodule commit"		
# go back to main repo
cd ..
# add subomodule repo as submodule
git submodule add ./submodule	
# git add new submodule files and configs
git add ./submodule .gitmodule		
# commit this change
git commit -m "add submodule"
# push to git server
git push origin master

On another Local Machine which want to clone this repo:

1 2	# clone a repo with all submoduel git clone --recursive git@yourserver:/dir/to/remote/server/main.git

Then you will have a repo named main with submodule named submodule.

VIEW THE POST >>