¶ [ssbsGAE]running web2py

2008-05-08 19:00

1. ssbsGAE

slow step by step GAE::

  • 慢慢使用GAE
  • 俺计划将基于GAE 的使用体验使用 `[ssbsGAE]` 的标签长期完整的记录分享下来 ;-)

1.1. web2py

为什么先选择了 `web2py`?

  • 因为俺比较懒散
  • web2py
  • Python web app. framework 中最 Rails 样的新兴实现!
  • 将核心引擎打造的足够`K.I.S.S` 自然使用之!
    • M ~ DB的ROM 足够快和全面
    • C ~ 完全OO而且可以在线编辑的控制层
    • V ~ 模板系统非常友好,可以直接嵌入 Py 脚本段!
    • D ~ 设计界面内置在系统中!
  • 而且文档齐全!

,;

1.2. zqlib

Zqlib. ~ 挖了N久的坑了!

  • 目标也一直在变化着
  • 现在就先成为自个儿的想法/代码/知识片段收集仓库吧
  • 算是比Blog 要自在,但是没有 wiki 开放的地儿,先

1.3. go!

  • 下载web2py:svn co http://web2py.googlecode.com/svn/trunk/ web2py-read-only
  • 直接就可以运行:

    ,;

    • 哗,还给了 GUI 的服务台控制器!

  • 直接对目录进行修减,在 GAE SDK 中试运行一下:

    ,;

    • 嗯嗯嗯,除了警告一切正常!
    • 参考:web2py in GAE ~ limodou
  • 上传应用:python appcfg.py update zqlib/

    ,;

    • 成了!

1.4. TODO

  1. 使用gae.db
  2. 使用 GBase
  3. 使用 reST/t2t
  4. 发布 RESTful 接口

  • t2t渲染:: 2010-10-09 02:21:36
  • 动力源自::txt2tags

§ 写于: Thu, 08 May 2008 | 永久链接;源文: rdf ,rss ,raw | 分类: /Zen/Google §
[MailMe] [Print] Creative Commons License

作品Zoom.Quiet创作,采用知识共享署名-相同方式共享 2.5 中国大陆许可协议进行许可。 基于zoomquiet.org上的作品创作。

¶ 文件系统选择

2008-04-23 21:43

1. Solaris 的FS决择

节译:Solaris Filesystem Choices 50%

OpenSolaris 10 已经给用户提供了一大堆存储相关的支持,而且秉承UNIX的一贯习俗, 都是经过严格测试了的,这里就四种通用文件系统进行分析,希望可以就部署方面给读者提供足够的信息以便最终选择:

1.1. UFS

UFS 忒有历史凫,从80年代开始就是BSD等UNIX系統的默认FS; 类似于 ext3 在 GNU/Linux 体系中的地位; Solaris 中的UFS来自 SunOS,而SunOS 中的UFS来自 BSD;

不久前,UFS还是Solaris 中唯一的FS,不同于HP, IBM, SGI, 以及 DEC; SUN直到90年代也没有自主发展下一代的FS; 原因有两:

  1. 多数情况下开发者需要第三方代码来支持新FS,而这需要许可
  2. 多数可以交易来的FS都是 Veritas 许可的(嘛意思?)

Solaris10 只能从UFS启动,未来将允许从ZFS启动;在OpenSolaris 已经可以了; 但是当前,所有Solaris 还是得至少有一个UFS分区;

UFS虽然是个技术,但是贵在稳定和足够快; 而且Sun 在其最后基础上进行了多方的优化; 从Solaris 7 开始支持日志,进入本世纪,从Solaris 9 开始成为了默认特性; 原先卷級日志是种效率不好的模型,但是有趣的是FreeBSD又重新加入了这种特性.

UFS已经加入了对RAID支持良好的Solaris卷管理.

2008UFSd准备进行什么修订? 除作启动之外,UFS足够好用了,将来可由ZFS替代, 当然看,UFS 对于数据库是个好选择(有普遍的基于文件系统权限控制的DB); 同时对于保守的有固定工作且不想花时间太多时间配置的SA也是个好选择;

1.2. ZFS

对ZFS 已经有N多报道了,同时也收到了从Linux 阵营习惯性的嘲笑.

ZFS 不是魔法,但是足够COOL 了. 我喜欢将 UFS/ext3 视作首代UNIX文件系统, 而 VxFS和XFS 视作二代FS, 那未 ZFS 就是第一个三代UNIX FS!

ZFS已不仅仅是个文件系统了. 实际算是混合文件系统+卷管理器. 以上功能的集成赋予了ZFS极大的灵活性. 同时也是著名的"rampant layering violation"来源. 不过千万记住,这只是开发特性.我从来没有在打开文件时见过"layering violation"

ZFS的混合意味着你可以管理不同传统方案中的存储. 你能将文件系统映射到分区,同时可以将另一个映射成逻辑巻,每个逻辑巻又涉及一个或是多个硬盘. 在ZFS 中所有硬盘分配在一个存储池中. 每个ZFS文件系统从池中使用所有硬盘,且文件系统不分卷,可以使用全部空间. 这样没有重定分区大小的烦恼,一切是自动调整的, 不断增长/收缩的文件系统不是靠谱的管理方式。

ZFS同时在文件系统级别提供了可靠性检验. 所有数据读/写都可以使用认证(提供了最严厉的SHA256), 失败时双备份是支持的(元数据是在单一硬盘,而数据是经典的RAID结构),

ZFS provides the most robust error checking of any filesystem available. All data and metadata is checksummed (SHA256 is available for the paranoid), and the checksum is validated on every read and write. If it fails and a second copy is available (metadata blocks are replicated even on single disk pools, and data is typically replicated by RAID), the second block is fetched and the corrupted block is replaced. This protects against not just bad disks, but bad controllers and fibre paths. On-disk changes are committed transactionally, so although traditional journaling is not used, on-disk state is always valid. There is no ZFS fsck program. ZFS pools may be scrubbed for errors (logical and checksum) without unmounting them.

The copy-on-write nature of ZFS provides for nearly free snapshot and clone functionality. Snapshotting a filesystem creates a point in time image of that filesystem, mounted on a dot directory in the filesystem's root. Any number of different snapshots may be mounted, and no separate logical volume is needed, as would be for LVM style snapshots. Unless disk space becomes tight, there is no reason not to keep your snapshots forever. A clone is essentially a writable snapshot and may be mounted anywhere. Thus, multiple filesystems may be created based on the same dataset and may then diverge from the base. This is useful for creating a dozen virtual machines in a second or two from an image. Each new VM will take up no space at all until it is changed.

These are just a few interesting features of ZFS. ZFS is not a perfect replacement for traditional filesystems yet - it lacks per-user quota support and performs differently than the usual UFS profile. But for typical applications, I think it is now the best option. Its administrative features and self-healing capability (especially when its built in RAID is used) are hard to beat.

1.3. SAM and QFS

SAM and QFS are different things but are closely coupled. QFS is Sun's cluster filesystem, meaning that the same filesystem may be simultaneously mounted by multiple systems. SAM is a hierarchical storage manager; it allows a set of disks to be used as a cache for a tape library. SAM and QFS are designed to work together, but each may be used separately.

QFS has some interesting features. A QFS filesystem may span multiple disks with no extra LVM needed to do striping or concatenation. When multiple disks are used, data may be striped or round-robined. Round-robin allocation means that each file is written to one or two disks in the set. This is useful since, unlike striping, participation by all disks is not needed to fetch a file - each disk may seek totally independently. QFS also allows metadata to be separated from data. In this way, a few disks may serve the random metadata workload while the rest serve a sequential data workload. Finally, as mentioned before, QFS is an asymmetric cluster filesystem.

QFS cannot manage its own RAID, besides striping. For this, you need a hardware controller, a traditional volume manager, or a raw ZFS volume.

SAM makes a much larger backing store (typically a tape library) look like a regular UNIX filesystem. This is accomplished by storing metadata and often-referenced data on disk, and migrating infrequently used data in and out of the disk cache as needed. SAM can be configured so that all data is staged out to tape, so that if the disk cache fails, the tapes may be used like a backup. Files staged off of the disk cache are stored in tar-like archives, so that potentially random access of small files can become sequential. This can make further backups much faster.

QFS may be used as a local or cluster filesystem for large-file intensive workloads like Oracle. SAM and QFS are often used for huge data sets such as those encountered in supercomputing. SAM and QFS are optional products and are not cheap, but they have recently been released into OpenSolaris.

1.4. VxFS

The Veritas filesystem and volume manager have their roots in a fault-tolerant proprietary minicomputer built by Veritas in the 1980s. They have been available for Solaris since at least 1993 and have been ported to AIX and Linux. They are integrated into HP-UX and SCO UNIX, and Veritas Volume Manager code has been used (and extensively modified) in Tru64 UNIX and even in Windows. Over the years, Veritas has made a lot of money licensing their tech, and not because it is cheap, but because it works.

VxFS has never been part of Solaris but, when UFS was the only option, it was a popular addition. VxVM and VxFS are tightly integrated. Through vxassist, one may shrink and grow filesystems and their underlying volumes with minimal trouble. VxVM provides online RAID relayout. If you have a RAID5 and want to turn it into a RAID10, no problem, no downtime. If you need more space, just convert it back to a RAID5. VxVM has a reputation for being cryptic, and to some extent it is, but it's not so bad and the flexibility is impressive.

VxFS is a fast, extent based, journaled, clusterable filesystem. In fact, it essentially introduced these features to the world, along with direct IO. Newer versions of VxFS and VxVM have the ability to do cross-platform disk sharing. If you ever wanted to unmount a volume from your AIX box and mount it on Linux or Solaris, now you can.

VxFS and VxVM are still closed source. A version is available from Symantec that is free on small servers, with limitations, but I imagine that most users still pay. Pricing starts around $2500 and can be shocking for larger machines. VxFS and VxVM are solid choices for critical infrastructure workloads, including databases.

2. 结论

Conclusion

These are the four major choices in the Solaris on-disk filesystem world. Other filesystems, such as ext2, have some degree of support in OpenSolaris, and FUSE is also being worked on. But if you are deploying a Solaris server, you are going to be using one or more of these four. I hope that you enjoyed this overview, and if you have any corrections or tales of UNIX filesystem history, please let me know.

About the Author

John Finigan is a Computer Science graduate student and IT professional specializing in backup and recovery technology. He is especially interested in the history of enterprise computing and in Cold War technology.

3. TODO


  • t2t渲染:: 2010-10-09 02:21:41
  • 动力源自::txt2tags

§ 写于: Wed, 23 Apr 2008 | 永久链接;源文: rdf ,rss ,raw | 分类: /oss §
[MailMe] [Print] Creative Commons License

作品Zoom.Quiet创作,采用知识共享署名-相同方式共享 2.5 中国大陆许可协议进行许可。 基于zoomquiet.org上的作品创作。

1. FF3

看周围M$ 用户都主动升迁到 FF2.0.0.14 超级稳定版本了,

但是Ubuntu7.10 的源中依然是 2.0.0.13+,有点郁rz..

1.1. SwiftFox 3.0pre

不过 SwiftFox 已到了 3.0pre! 通过 apt 立即可以使用:

1.2. 探查

但是插件不能使用Nightly Tester Tools 轻易全开... 使用 安全模式::

swiftfox -safe-mode
  • 关闭所有 扩展和插件后,逐一尝试,确认最小可用组合::

1.2.1. 配置

启用扩展: [16]

1.3. 成了!

开始快乐的使用!

. ;


  • t2t渲染:: 2010-10-09 02:21:41
  • 动力源自::txt2tags

§ 写于: Mon, 21 Apr 2008 | 永久链接;源文: rdf ,rss ,raw | 分类: /oss/Mozilla/FireFox §
[MailMe] [Print] Creative Commons License

作品Zoom.Quiet创作,采用知识共享署名-相同方式共享 2.5 中国大陆许可协议进行许可。 基于zoomquiet.org上的作品创作。

¶ Hardy Heron

2008-04-15 10:15

1. 期待,但不等待

升级!需要理由嘛?

  • 不需要嘛?
    • 需要嘛?! ...

其实只是心理原因;-)
  • 7.10 使用非常舒服
  • 8.04 也没有ZFS哪
  • 考虑FreeBSD ing..
  • 不过,不跳票的 Ubuntu HH 还是非常想的,如果:
    • 字体更加好了
    • FF3支持所有主要插件了
    • 输入法默认是 bridge-scim 了
    • ...

      . ;

  • t2t渲染:: 2010-10-09 02:21:41
  • 动力源自::txt2tags

§ 写于: Tue, 15 Apr 2008 | 永久链接;源文: rdf ,rss ,raw | 分类: /oss/Ubuntu §
[MailMe] [Print] Creative Commons License

作品Zoom.Quiet创作,采用知识共享署名-相同方式共享 2.5 中国大陆许可协议进行许可。 基于zoomquiet.org上的作品创作。

¶ [LvL]对错录

2008-04-08 00:21

1. 冇好错

真的哪,放开心灵去想和感受的话的确的哪...

1.1. 相识

  • 妳冇错: 追求想要的快乐
  • 愿妳好: 妳应该享受快乐
  • 错在我: 没有及时明确我的态度,暧昧是至高技巧,不是我们可以消受的..
  • 呔! 都这会儿了,早过暧昧阶段了,一起快乐就好!

  • 妳冇错: 追求想要的关爱
  • 愿妳好: 妳应该得到关爱
  • 错在我: 除了技术/知识,没有受到过关怀人的训练,作不出来..
  • 呔! 都这会儿了,跟着我一起作关怀的事儿就好!

  • 妳冇错: 追求渴望的爱情
  • 愿妳好: 妳应该拥有爱情
  • 错在我: 理工的训练让我们不相信爱情,不相信爱情的人无法创造爱情的吧?
  • 呔! 都这会儿了,谁问这种小姑娘的问题,你只准和我在一起就好!

1.2. 相试

  • 妳冇错: 追求想要的性爱
  • 愿妳好: 妳应该体验高潮
  • 错在我: 从来关注自个儿的感觉,真正要配合体验时,无从下手哪~怎么读懂妳?
  • 呔! 都这会儿了,这有手册,一起来尝试就好!

  • 妳冇错: 追求亲昵的厮守
  • 愿妳好: 妳应该有人陪伴
  • 错在我: 享受惯了孤独,无法想象有人分享独处时的自在..
  • 呔! 都这会儿了,还装,在一起时只要你讲,我不来打挠就好!

  • 妳冇错: 追求不再有寂寞
  • 愿妳好: 妳应该快乐平和
  • 错在我: 不相信寂寞的人,无法理解这种感受,就算是担心也不知道怎么作..
  • 呔! 都这会儿了,只要你陪我就好!

1.3. 相望

  • 妳冇错: 追求相互的守望
  • 愿妳好: 妳应被认真守望
  • 错在我: 守望需要距离,这么接近,守望只是表演了吧
  • 呔! 都这会儿了,常常短信我就好!

  • 妳冇错: 追求全天的挂念
  • 愿妳好: 妳的确值得挂念
  • 错在我: 我有我生活,必须奋斗关注的事儿太多,何时挂念?
  • 呔! 都这会儿了,到处有网络你逃不了就好!

  • 妳冇错: 追求琐细的呵护
  • 愿妳好: 妳应被温柔呵护
  • 错在我: 对自个儿都执行放养政策的,如何学会呵护?
  • 呔! 都这会儿了,听众命令就好!

1.4. 相示

  • 妳冇错: 追求平静的照顾
  • 愿妳好: 妳应该得到照顾
  • 错在我: 人在江湖身不由己!工作日之外就是加班日!只享受妳的照顾的话,又与心何忍?
  • 呔! 都这会儿了,我喜欢照顾你就好!

  • 妳冇错: 追求游玩的畅快
  • 愿妳好: 妳应该享受生活
  • 错在我: 在生存中挣扎习惯了,没有享受过生活的我,如何配合妳?
  • 呔! 都这会儿了,放开心情一起来体验就好!

  • 妳冇错: 追求公开的相守
  • 愿妳好: 妳应被正大相守
  • 错在我: 正大光明的被所有人监察,已经吓退过无数的人了,留白天地才宽..
  • 呔! 都这会儿了,只要你心里有我就好!

1.5. 相世

  • 妳冇错: 追求永久的承诺
  • 愿妳好: 妳应该得到承诺
  • 错在我: 不相信永久的我,如何给出承诺?
  • 呔! 都这会儿了,作到以上几点就好!

  • 妳冇错: 追求永恒的认可
  • 愿妳好: 妳应该获得认可
  • 错在我: 不相信永恒的我,在被BS后,如何生存下去?
  • 呔! 都这会儿了,担心也是以后就好!

  • 妳冇错: 追求永远的想念
  • 愿妳好: 妳应该受到想念
  • 错在我: 没有想念过谁的我,怎么知道哪种感觉是想念?
  • 呔! 都这会儿了,管什么感觉,在一起就好!

1.6. 相逝

  • 妳冇错: 追求甜蜜的关怀
  • 愿妳好: 妳的甜蜜必有回报
  • 错在我: 习惯苦熬的我如何回报甜蜜?
  • 呔! 都这会儿了,什么是你的甜蜜我来发现就好!

  • 妳冇错: 追求舒心的生活
  • 愿妳好: 妳的生活必能舒畅
  • 错在我: 一向被生活享受的我,从何舒畅你的生活?
  • 呔! 都这会儿了,笨!有你就好!

  • 妳冇错: 追求无悔的逝去
  • 愿妳好: 妳的一生必应无悔
  • 错在我: 但是怎么保证不在你之前逝去?
  • 呔! 都这会儿了,猪!那我自杀就好!

.. .. ..

火星人和水星人的碰面,只会令地球更加危险


动力源自::txt2tags

,living ,Quiet


§ 写于: Tue, 08 Apr 2008 | 永久链接;源文: rdf ,rss ,raw | 分类: /Quiet/living §
[MailMe] [Print] Creative Commons License

作品Zoom.Quiet创作,采用知识共享署名-相同方式共享 2.5 中国大陆许可协议进行许可。 基于zoomquiet.org上的作品创作。